Demodulation reference signal indicating and receiving methods, transmit end, and receive end

ABSTRACT

A demodulation reference signal (DMRS) indicating method, a DMRS receiving method, and an apparatus are described. A transmit end determines, from a plurality of groups of demodulation reference signal DMRS configuration information, DMRS configuration information corresponding to a current DMRS transmission scheme. The transmit end obtains DMRS indication information based on the DMRS configuration information, where each group of DMRS configuration information includes a plurality of pieces of DMRSs configuration information. The transmit end sends the DMRS indication information. The described method and the apparatus are implemented to match a plurality of New Radio (NR) scenarios. The described operations can satisfy a requirement for transmitting more layers of data and reduce indication overheads.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2018/096201, filed on Jul. 19, 2018, which claims priority toChinese Patent Application No. 201710686645.9, filed on Aug. 11, 2017and Chinese Patent Application No. 201711147995.4, filed on Nov. 17,2017. The disclosures of the aforementioned applications are herebyincorporated by reference in their entireties.

TECHNICAL FIELD

This application relates to the communications field, and in particular,to demodulation reference signal (DMRS) indicating and receivingmethods, a transmit end, and a receive end.

BACKGROUND

In a multiple-input multiple-output (MIMO) technology, resources inspatial dimension are used, so that a signal may spatially obtain arraygains, multiplexing and diversity gains, and interference cancellationgains without increasing a system bandwidth, thereby exponentiallyimproving a capacity and spectral efficiency of a communications system.For example, in a Long Term Evolution (LTE) system, a single usersupports multiplexing of a maximum of eight layers of orthogonal DMRSports, and a DMRS occupies 24 resource elements (Res). Specifically, infrequency domain, DMRS ports may be mapped onto the zeroth, the first,the fifth, the sixth, the tenth, and the eleventh subcarriers in eachresource block (RB) pair, and in time domain, DMRS ports may be mappedonto the fifth, the sixth, the twelfth, and the thirteenth symbols ineach subframe, as shown in FIG. 1.

However, as people have increasingly high communication requirementssuch as a high rate, high reliability, and a low latency, moderncommunications systems will always face challenges of a larger capacity,wider coverage, and a lower latency. These requirements are also keyrequirements on a New Radio (NR) future network.

In a demodulation process at a receive end in the communicationssystems, compared with incoherent demodulation, coherent demodulationhas better performance, and has a performance gain of approximately 3dB. Therefore, the coherent demodulation is more widely used in themodern communications systems. However, modulation on each carrier in anorthogonal frequency-division multiplexing (OFDM) system is to suppressthe carrier. Reference signals (RS), also referred to as pilot signals,are required during the coherent demodulation at the receive end. In anOFDM symbol, they are distributed on different resource units intwo-dimensional time-frequency space, and have amplitudes and phasesthat are known. Likewise, in a MIMO system, each transmitting antenna (avirtual antenna or a physical antenna) has an independent data channel.Based on a predicted RS signal, a receiver performs channel estimationfor each transmitting antenna, and restores sent data based on theestimation.

The channel estimation is a process in which a received signal isreconstructed to compensate for channel fading and noise. In thisprocess, time-domain and frequency-domain changes of a channel aretracked by using RSs predicted by a transmitter and a receiver. Forexample, to implement data demodulation in a high-order multi-antennasystem, an LTE-A system defines a demodulation reference signal (DMRS).The reference signal is used for demodulating uplink and downlinkcontrol channels and a data channel such as a physical downlink sharedchannel (PDSCH).

A same preprocessing manner is used for the DMRS and user data.Characteristics of the DMRS are as follows:

(1) The DMRS is user-specific. To be specific, a same precoding matrixis used for each piece of terminal data and a demodulation referencesignal corresponding to the terminal data.

(2) From a perspective of a network side, DMRSs transmitted on layersare mutually orthogonal.

(3) The DMRS is usually used to support beamforming and precodingtechnologies, and therefore, is sent only on a scheduled resource block,where a quantity of sent DMRS ports is related to a quantity of datastreams (or referred to as a quantity of layers). The DMRS ports are inone-to-one correspondence with antenna ports rather than a quantity ofphysical antennas. The quantity of DMRS ports is less than or equal tothe quantity of physical antennas, and the two quantities are associatedthrough layer mapping and precoding.

In a current standard, a maximum quantity of orthogonal data streamsthat can be supported by DMRSs used on a downlink is 8, resourceoverheads of each PRB pair are 24 REs, and the DMRSs are distributed inall PRBs in forms of block pilots. Each port (port) occupies 12 REs. Inother words, densities of the ports are the same. In addition, a designof a DMRS sequence is determined based on the density of each port, andtherefore, a length of the DMRS sequence is a fixed value.

However, New Radio (NR) supports more diverse scenarios, and thereforesupports a plurality of configurations (patterns). For example, to adaptto data transmission in different frequency bands, multiplexing modesdiffer greatly. In addition, to further satisfy a larger-capacitytransmission requirement, a maximum quantity of orthogonal data streamsthat can be supported by DMRSs on a data channel is greater than 8. Forexample, in the 3GPP RAN1 #88bis meeting, it was agreed that 12orthogonal DMRS ports are supported.

Moreover, in the LTE system, all transceiver antennas have a very lowdimension. Therefore, a multiple user (MU) dimension supported during MUmatching is relatively low. For example, during MU scheduling, a maximumof two layers are allowed for a single user, and there are a total offour orthogonal layers. Compared with the LTE system, in a futurenetwork, four receive antennas may be necessary for future UE. In thiscase, an MU dimension changes.

During actual transmission, a base station needs to notify a terminal ofinformation such as a quantity of layers that are allocated by the basestation, a DMRS port number, a sequence configuration, and amultiplexing mode. In LTE, all of the information is indicated by usingdownlink control information (DCI). However, NR has supported aplurality of patterns, there are a plurality of variations in a quantityof ports, a multiplexing mode, and a mapping rule, and very highoverheads are caused if the DCI-based indication manner in LTE is stillused. Therefore, how to indicate a DMRS in NR is a technical problemthat urgently needs to be resolved.

SUMMARY

To resolve the foregoing technical problem, this application provides ademodulation reference signal indicating and receiving method and anapparatus.

A quantity of orthogonal ports that are for code division multiplexing(CDM) type multiplexing and that can be supported by an MU-MIMO scenarioin an NR system is different from that in LTE, and a maximum of 12orthogonal ports can be supported. Therefore, a manner in LTE is nolonger applicable in which a terminal is notified, based on only a DMRSconfiguration information table, of information such as a quantity oflayers that are allocated in LTE, an orthogonal DMRS port number, asequence configuration, and a multiplexing mode. In embodiments of thisapplication, a plurality of groups of DMRS configuration information aredesigned to respectively match DMRS transmission requirements indifferent scenarios in a future network (new radio, or NR).

According to a first aspect, a demodulation reference signal indicatingand receiving method provided in this application includes: determining,by a transmit end from a plurality of groups of DMRS configurationinformation, DMRS configuration information corresponding to a currentDMRS transmission scheme, and obtaining DMRS indication informationbased on the DMRS configuration information, where each group of DMRSconfiguration information includes a plurality of pieces of DMRSconfiguration information; sending the DMRS indication information to areceive end; and assisting, by the receive end, in demodulating dataafter receiving the DMRS indication information.

In this embodiment of this application, the current DMRS transmissionscheme is indicated by using the indication information, and differentDMRS transmission schemes correspond to different maximum supportedorthogonal-port quantities, or correspond to different DMRS patterns ordifferent DMRS configuration types.

The maximum supported orthogonal-port quantities in DMRS configurationinformation corresponding to the different DMRS transmission schemes aredifferent.

Lengths of DMRS indication information corresponding to the differentDMRS transmission schemes are different.

A plurality of DMRS ports in the plurality of pieces of DMRSconfiguration information belong to different code division multiplexing(CDM) groups, where different CDM groups satisfy a non-quasi co-location(QCL) relationship.

In an implementation, for different maximum supported orthogonal-portquantities, different groups of DMRS configuration information may beconfigured. The group of DMRS configuration information includes aplurality of pieces of DMRS configuration information. For example, inMIMO scenarios in which a maximum supported orthogonal-port quantity is4, a maximum supported orthogonal-port quantity is 6, a maximumsupported orthogonal-port quantity is 8, and a maximum supportedorthogonal-port quantity is 12, corresponding DMRS configurationinformation is separately configured. The DMRS configuration informationis used to inform the receive end of an orthogonal DMRS port number, asequence configuration, a multiplexing mode, and the like that can beused by the receive end, thereby correctly decoding data.

In another implementation, the DMRS configuration information isconfigured for different DMRS patterns. Usually, one DMRS patterncorresponds to one MIMO scenario that supports a maximum supportedorthogonal-port quantity or a maximum supportedorthogonal-transmission-layer quantity. The DMRS pattern shows aquantity of orthogonal port groups supported by the MIMO scenario and aquantity of resource units included in each orthogonal port group.Therefore, configuring different DMRS configuration information fordifferent DMRS patterns can also enable the receive end to know anorthogonal DMRS port number, a sequence configuration, a multiplexingmode, and the like that can be used by the receive end, therebycorrectly decoding data.

In an implementation of the first aspect, the DMRS configurationinformation may be presented by a protocol-agreed table, and a specificimplementation form thereof may be a downlink control information (DCI)table. A plurality of DCI tables include at least one group of differentDMRS configuration information. One group of DMRS configurationinformation includes a plurality of pieces of DMRS configurationinformation, and is presented by one table. The table is referred to asa DMRS configuration information table in this specification.

The DMRS transmission scheme corresponding to the DMRS indicationinformation is sent by using higher layer signaling, for example, radioresource control (RRC) signaling. Certainly, the DMRS configurationinformation may alternatively be bound with another configurationparameter, for example, a carrier frequency, a carrier spacing, or aframe structure, corresponding to a scenario. In this way, the DMRSindication information can be sent by using DCI signaling or a mediaaccess control control element (MAC CE).

During specific implementation, each DMRS configuration informationtable corresponds to a different maximum supported orthogonal-portquantity (port). For example, the maximum supported orthogonal-portquantity may be at least two of {4, 6, 8, 12}.

In another implementation, each DMRS configuration information table maycorrespond to a different DMRS pattern or DMRS configuration type.

In an implementation, in the DMRS configuration information table,column arrangement design is performed based on an orthogonal portgroup. For example, column arrangement design is performed on anorthogonal port combination having four or less transmission layers andan orthogonal port combination having more than four transmissionlayers.

In an implementation, when the DMRS configuration information ispresented in a form of a DMRS configuration information table, divisionmay be performed based on a codeword number, or may be performed basedon a total maximum supported orthogonal-port quantity or a quantity oftransmission layers at the receive end, instead of a codeword number.Specifically, division may be performed based on a ratio.

The DMRS configuration information table further includes indicationinformation of a total quantity of orthogonal ports, and the indicationinformation may indicate a quantity of all orthogonal ports that arepossibly actually presented or a quantized value of a quantity of allorthogonal ports that are possibly actually presented. The quantizedvalue of the quantity of all the orthogonal ports may be informationabout a quantity of orthogonal DMRS layers, indication information of anorthogonal DMRS antenna port set, CDM group information of an orthogonalDMRS antenna port, or information generated based on a CDM group size.It should be understood that the total quantity of orthogonal ports isthe same as a total quantity of orthogonal DMRS transmission layers. TheCDM group information of the orthogonal DMRS antenna port may be anumber of CDM groups, a number of CDM groups, or CDM group stateinformation.

It should be noted that the plurality of groups of DMRS configurationinformation may be presented by using a general information table. Inother words, a plurality of DMRS configuration information tables may bea general information table, the general information table supports themaximum supported orthogonal-port quantity, and the plurality of DMRSconfiguration information tables are subsets of the general informationtable. A subset may be selected from the general information table basedon the maximum supported orthogonal-port quantity, the DMRS pattern, orthe higher layer signaling.

In the DMRS configuration information, the CDM group information of theorthogonal DMRS antenna port is CDM group state information, a CDM groupsequence number, a number of CDM groups, or a number of CDM groups. Inan implementation, the number of CDM groups is a quantity of CDM groupoccupied/scheduled (co-scheduled) in a system.

The DMRS configuration information further includes DMRS symbolinformation.

An available range of the DMRS configuration information is bound to aparameter indicating a maximum number of symbols of a DMRS in radioresource control signaling RRC.

The available range of the DMRS configuration information is bound witha parameter that is in the Radio Resource Control RRC signaling and thatindicates the maximum number of symbols of the DMRS.

In cases of different maximum symbol quantities of the DMRS, lengths ofdownlink control information DCI signaling for performing DMRS portscheduling are different, quantities of bits in DCI are different, orDCI fields are different.

When single-user SU scheduling is performed by using the DMRSconfiguration information, FDM scheduling is first performed in two CDMgroups. A quantity of orthogonal ports that are for CDM multiplexing andthat can be supported by a MIMO scenario in an NR system is differentfrom that in LTE, and a maximum of 12 orthogonal ports can be supported.The terminal usually needs to know port information of another terminalthat is co-scheduled, to learn of RE locations that are occupied byDMRSs on ports used by the another terminal and at which no data of theterminal is transmitted. If the terminal cannot learn of theinformation, the terminal may use a DMRS from another user as the dataof the terminal for decoding, leading to a decoding error. An effectiveDMRS rate matching indicating manner is required to show how to enable aterminal to know ports on which DMRSs are occupied. To resolve thetechnical problem, this application provides a demodulation referencesignal indicating method and receiving method, including: generating, bya transmit end, demodulation reference signal DMRS indicationinformation, where the DMRS indication information is used to indicate aresource that is not occupied by DMRS and that is in resources availablefor carrying a DMRS; sending, by the transmit end, the DMRS indicationinformation to a receive end; and demodulating, by the receive end basedon the DMRS indication information, data on the resource that is notoccupied by DMRS, where specifically, the receive end needs to receivethe DMRS indication information by using downlink control information ora Media Access Control control element.

The receive end obtains, based on the received DMRS indicationinformation, a current quantized quantity of orthogonal transmissionlayers, a combination of currently used port group states, anorthogonal-transmission-layer quantity or a port group state that is notcurrently used by the receive end, or a resource unit that needs to bemuted, to obtain the resource that is not occupied by DMRS and that isin the resources available for carrying a DMRS.

In an implementation, before receiving the DMRS indication information,the receive end further receives DMRS transmission scheme indicationinformation indicating current DMRS transmission scheme. Different DMRStransmission schemes correspond to different maximum supportedorthogonal-port quantities, or correspond to different DMRS patterns ordifferent DMRS configuration types.

It should be understood that, the DMRS transmission scheme is reflectedby using a DMRS pattern, a DMRS configuration type, or a maximumsupported orthogonal-port quantity.

It should be noted that herein, the maximum supported orthogonal-portquantity is a maximum quantity of orthogonal ports that can be scheduledby the transmit end in a current frame. For example, a 12-port DMRSpattern can be used. However, a current maximum quantity of scheduledports is only 4, and the maximum supported orthogonal-port quantity isrelated to base station scheduling, and is less than or equal to amaximum quantity of orthogonal ports supported by the DMRS pattern.

For example, in an MU-MIMO scenario in which a maximum supportedorthogonal-port quantity is 4, 6, 8, or 12, or in a scenario in which amaximum supported non-orthogonal-port quantity is 8, 12, 16, or 24 (ascenario with two scrambling codes), corresponding DMRS indicationinformation is separately configured. In other words, based on differentmaximum supported orthogonal-port quantities, corresponding DMRSindication information is separately configured. The indicationinformation is used to inform the receive end of resource units on atime-frequency resource that are occupied by DMRSs of other users and onwhich no data of the receive end exists. In this way, the receive endcan avoid these resource units during data demodulation, to correctlydecode data.

In another implementation, the DMRS indication information is configuredfor different DMRS patterns, or may be configured in correspondence witha quantity of DMRS port groups in a DMRS pattern (for example, there maybe two tables respectively corresponding to DMRS patterns that includetwo or three DMRS port groups).

Usually, one DMRS pattern corresponds to one MU-MIMO scenario supportinga maximum supported orthogonal-port quantity. The DMRS pattern shows aquantity of orthogonal CDM port groups supported by the MU-MIMO scenarioand a quantity of resource units included in each port group. Therefore,different indication information is configured for different DMRSpatterns.

In still another implementation, the indication information may befurther configured for a DMRS configuration type.

In all of the foregoing implementations, the receive end may be informedof resource units on a time-frequency resource that are occupied byDMRSs of other users, so that the receive end can correctly decode data.

In an implementation, the receive end needs to receive a signaledcorrespondence between the DMRS indication information and the resourcethat is not occupied by DMRS and that is in the resources available forcarrying a DMRS. The signaling described herein is usually higher layersignaling, for example, RRC signaling.

In another implementation, the receive end further stores DMRSconfiguration information. In other words, a correspondence between theDMRS indication information and the resource that is not occupied byDMRS and that is in the resources available for carrying a DMRS can befound in the locally stored DMRS configuration information.

In this embodiment of this application, the DMRS configurationinformation further includes indication information of a total quantityof orthogonal ports, and the indication information for the totalquantity of orthogonal ports may indicate a quantity of all orthogonalports that are possibly actually presented or a quantized value of aquantity of all orthogonal ports that are possibly actually presented.The quantized value of the quantity of all the orthogonal ports isinformation about a quantity of orthogonal DMRS layers, indicationinformation of an orthogonal DMRS antenna port set, CDM groupinformation of an orthogonal DMRS antenna port, or information generatedbased on a CDM group size. The CDM group information of the orthogonalDMRS antenna port is a number of CDM groups, a number of CDM groups, orCDM group state information.

In the information about the quantity of orthogonal DMRS layers, thequantity of orthogonal DMRS layers is an integer multiple of a quantityof DMRS antenna ports in a CDM group, an integer multiple of a quantityof DMRS antenna ports having consecutive sequence numbers in a CDMgroup, or a value of a sequence number of a DMRS antenna port in a CDMgroup. During specific implementation, the information about thequantity of DMRS layers may be information about a quantity of DMRSlayers that are quantized through grading. In the information about thequantity of DMRS layers that are quantized through grading, the quantityof DMRS layers may be an integer multiple of a quantity of DMRS antennaports in a CDM group. For example, for a DMRS pattern including two DMRSantenna port groups, assuming that DMRS ports included in a port group 1are 11, 2, 3, 41, and DMRS ports included in a port group 2 are {5, 6,7, 8}, the port group 1 and the port group 2 may be quantized into fourlayers and eight layers. In addition, in the information about thequantity of DMRS layers, the quantity of DMRS layers may alternativelybe an integer multiple of a quantity of DMRS antenna ports havingconsecutive sequence numbers in ascending order in a CDM group. Forexample, CDM groups {1, 2, 5, 7} and {3, 4, 6, 8} may be quantized intotwo layers and four layers. All of the information can enable thereceive end to identify which resource units are occupied by the DMRS ofthe receive end, and which resource units are occupied by DMRSs of otherreceive ends that implement CDM multiplexing. Remaining resource unitsare used for data transmission related to the receive end. Therefore,the receive end demodulates data on a corresponding resource unit.

A reason for using the quantized value of the quantity of orthogonaltransmission layers is that if a specific quantity of transmissionlayers of the receive end needs to be indicated, for example, iftransmission layer quantities {1, 2, 3, 4} need to be separatelyindicated, two bits are required for indication. When the transmissionlayer quantities {1, 2, 3, 4} are quantized, for example, quantizedupward into a transmission layer quantity 4, or quantized downward intoa transmission layer quantity 1, or when the transmission layerquantities {1, 2, 3, 4} are represented by 2 or 3, only one bit isrequired to indicate the quantized value of the quantity of transmissionlayers. For example, 0 is used to represent a quantized value 4 of thetransmission layer quantity. Therefore, indication overheads can bereduced.

Based on the foregoing principle, in this embodiment of thisapplication, the DMRS indication information may indicate the quantizedvalue of the quantity of orthogonal transmission layers. One manner isimplicit indication, and another manner is explicit indication.

In the implicit indication solution, the quantized value of the quantityof orthogonal transmission layers is configured in a DMRS configurationinformation table, and the indication information is indicated by usingDMRS indication information (a value) in the DMRS configurationinformation table. The DMRS configuration information table may besimilar to that in LTE. For example, the DMRS indication information isa quantity of antenna ports, a scrambling identification (scramblingidentification), and an indication of a quantity of transmission layersthat are in LTE. The DMRS configuration information table may furtherinclude at least one of a DMRS port quantity, a port index, sequencegeneration information, and a CDM type. Based on this, the quantizedvalue of the quantity of transmission layers is added. The DMRSconfiguration information table may be stored at both the transmit endand the receive end. The transmit end sends the indication informationto the receive end. It should be understood that, the transmit end sendsoriginal DCI signaling in LTE (because the signaling in LTE is stillused, the DCI signaling may not be named as indication information, butmay indicate a rate matching solution) to the receive end. The receiveend obtains, based on the signaling, port information of the receive endand a total quantized quantity of transmission layers in a system, andcalculates, with reference to the two pieces of information, a port usedby another receive end. In other words, the receive end identifies whichresource units are used for DMRS transmission at the receive end andwhich resource units are used for DMRS transmission at other receiveends that implement CDM multiplexing. Remaining resource units are usedfor data transmission related to the receive end. Therefore, the receiveend demodulates data on a corresponding resource unit.

In the explicit signaling indication solution, a correspondence betweenthe indication information and the quantized value of the quantity oforthogonal transmission layers exists independently of a DMRSconfiguration information table in LTE. In other words, thecorrespondence between the indication information and the quantizedvalue of the quantity of transmission layers is not implied in the DMRSconfiguration information table. Therefore, in addition to the DMRSconfiguration information table, the transmit end and the receive endfurther separately store a correspondence configuration table betweenthe indication information and the quantized value of the quantity oftransmission layers (or the information table may be configured throughRRC). The correspondence configuration table exists independently of theDMRS configuration information table. The transmit end sends rateconfiguration indication information to the receive end through implicitsignaling. The receive end uses the indication information as an index,and searches the correspondence configuration table for a correspondingquantized value of a quantity of transmission layers. The receive endcombines the quantized value of the quantity of transmission layers withthe DMRS configuration information table, to identify which resourceunits are occupied by the DMRS of the receive end, and which resourceunits are occupied by DMRSs of other receive ends that implement CDMmultiplexing. Remaining resource units are used for data transmissionrelated to the receive end. Therefore, the receive end demodulates dataon a corresponding resource unit.

It should be noted that indication information having a same value maycorrespond to quantized values of different quantities of transmissionlayers. Therefore, the correspondence between the indication informationand the quantized value of the quantity of transmission layers mayalternatively be indicated through separate signaling.

It should be understood that, in the explicit indication solution, thequantized quantity of transmission layers is indicated by using theindication information. The receive end receives two pieces ofsignaling, where one piece of signaling is DMRS DCI signaling in LTE,and the other piece of signaling is indication information signaling(which may also be referred to as rate matching signaling in thisspecification) used to transmit a current quantized quantity oftransmission layers.

It may be understood that, regardless of the implicit indicationsolution or the explicit indication solution, the DMRS indicationinformation may be sent to the receive end as independent signaling ormay be carried in downlink signaling for sending, for example, downlinkcontrol information DCI. This is not limited herein.

In an implementation, whether to send the DMRS indication information isdetermined based on a codeword quantity. For example, in a case of onecodeword, signaling is triggered to send the DMRS indicationinformation, but in a case of two codewords, the signaling is not sent.This is because in the case of one codeword, there are a single-user(SU) scenario and a multi-user (MU) scenario, while in the case of twocodewords, there is only single-user (SU) scenario. In the single usermultiple-input multiple-output (SU-MIMO) scenario corresponding to thetwo codewords, when the transmit end, for example, a base station,communicates with only one receive end (a terminal), only information(RS, control signaling, data, or the like) of the terminal istransmitted on a time-frequency resource. In this case, the terminal candirectly learn of locations of DMRS REs of the terminal based on theinformation of the terminal (for example, a port, a quantity of layers,or the like of the terminal), and avoid the REs during data decoding.Therefore, there is no DMRS rate matching problem in the SU scenario.

According to a second aspect of the embodiments of this application, aDMRS rate matching indicating and receiving method is further provided.The method includes: in a 2-PDCCH scenario, two TRPs in a non-QCL groupare used, where each TRP mutes a resource unit corresponding to a DMRSthat is of a QCL group and that is not used by the TRP, and thentransmits data, one TRP may have DMRSs of one or more QCL groups, andthis behavior may be a default operation; or in a 1-PDCCH scenario, atransmit end needs to send DMRS indication information to a receive end,where the DMRS indication information indicates a resource unitcorresponding to a DMRS in one or more QCL groups used by the transmitend.

In the 2-PDCCH scenario or the 1-PDCCH scenario, the transmit endnotifies the receive end also in two manners.

Manner 1: The transmit end sends DMRS indication information to thereceive end. The DMRS indication information indicates, in the 2-PDCCHscenario, a current quantized quantity of transmission layers in a DMRSport that may be used by the TRP, or in the 1-PDCCH scenario, a totalquantity of layers that may be used by a coordinating TRP in a currentsystem.

Manner 2: In the 2-PDCCH scenario, for different DMRS patterns, thereceive end may use a DMRS configuration information table thatcorresponds to the DMRS patterns and that includes DMRS indicationinformation, to perform rate matching. It should be noted that, the DMRSpattern herein is a DMRS pattern including DMRS ports in a QCL groupthat may be used by the TRP. Alternatively, in the 1-PDCCH scenario, acoordinating TRP may use a DMRS pattern including DMRS ports in aplurality of QCL groups.

It should be noted that, a plurality of DMRS configuration informationtables may alternatively be a general information table, the generalinformation table supports a maximum supported port quantity, and theplurality of DMRS configuration information tables are subsets of thegeneral information table. A subset may be selected from the generalinformation table based on the maximum supported port quantity, the DMRSpattern, or higher layer signaling.

In an implementation in which the DMRS indication information indicatesDMRS antenna port set information, the DMRS antenna port set informationindicates a status of an occupied DMRS antenna port group based on anactual quantity of DMRS layers that are scheduled in a current system.For example, a port group 1 is {1, 2, 3, 4}, and a port group 2 is {5,6, 7, 8}. It is assumed that the base station performs scheduling inascending order of DMRS port numbers. When a quantity of scheduledlayers is 4, it indicates that the port group 1 is occupied. When thequantity of scheduled layers is greater than 4, it indicates that theport groups 1 and 2 are occupied. This is only an example, and specificport number grouping and base station scheduling are not limited herein.

In an implementation in which the DMRS indication information indicatescode division multiplexing CDM group information of the DMRS antennaport, the code division multiplexing CDM group information includes CDMport group information that is of a DMRS antenna port and that is notused by the receive end, or a sum of DMRS antenna port group informationused by the receive end and DMRS antenna port group information not usedby the receive end.

The DMRS CDM port group information not used by the receive end mayinclude at least one of the following states:

1. Data can be transmitted on all DMRS RE locations (SU);

2. All DMRS RE locations are occupied (MU). This case includes: thereceive end uses one (or two) DMRS port CDM group and other two (or one)CDM groups are occupied, or the receive end uses two DMRS port CDMgroups and another one CDM group is occupied.

3. A larger one of two port groups that are not of the receive end ismuted (MU, where UE uses one port group); and

4. A smaller one of two port groups that are not of the receive end ismuted (MU, where UE uses one port group).

It should be understood that, “larger” and “smaller” may be defined as acomparison between maximum or minimum port numbers in two CDM portgroups (in other words, a relative relationship between DMRS port groupsthat are not of UE).

During specific implementation, for the states 3 and 4, no comparisonbetween “larger” and “smaller” may exist. For example, the DMRS CDM portgroup information may be a port number included in a port group or anumber of a port group.

The DMRS CDM port group information not used by the receive end may bebound with a DMRS type (a DMRS configuration/Type 1/A or 2/B), or boundwith a quantity (2 or 3) of CDM groups included in a pattern.

This manner of indicating the DMRS port group status not used by thereceive end can further reduce indication overheads. In addition, thismanner can further support a plurality of scenarios and has betteruniversality. For example, 1-PDCCH NC-JT, dynamic TDD, and 2-PDCCH NC-JTmay be directly supported, and an existing instruction has few changes.

According to another aspect, an embodiment of this application providesa transmit end. The transmit end includes: a processor, for determining,from a plurality of groups of demodulation reference signal DMRSconfiguration information, DMRS configuration information correspondingto a current DMRS transmission scheme, and obtaining DMRS indicationinformation based on the DMRS configuration information, where eachgroup of DMRS configuration information includes a plurality of piecesof DMRS configuration information; and a transceiver, for sending theDMRS indication information.

According to another aspect, an embodiment of this application providesa transmit end, including: a processor, for generating demodulationreference signal DMRS indication information, where the DMRS indicationinformation corresponds to a maximum supported port quantity, a DMRSpattern, or a DMRS configuration type; and a transceiver, for sendingthe DMRS indication information.

According to another aspect, this application provides a receive end,including: a transceiver, for receiving demodulation reference signalDMRS indication information sent by a transmit end, where the DMRSindication information is obtained by the transmit end based ondemodulation reference signal DMRS configuration information, the DMRSconfiguration information is determined by the transmit end from aplurality of groups of DMRS configuration information based on a currentDMRS transmission scheme, and each group of DMRS configurationinformation includes a plurality of pieces of DMRS configurationinformation; and a processor, configured to obtain the DMRSconfiguration information and assisting in demodulating data, based onthe DMRS indication information received by the transceiver.

According to still another aspect, this application provides anothertransmit end, including: a processor, for generating demodulationreference signal DMRS indication information, where the DMRS indicationinformation is used to indicate a resource that is not occupied by DMRSand that is in resources available for carrying a DMRS; and atransceiver, for sending the DMRS indication information.

According to still another aspect, this application provides anotherreceive end, including: a transceiver, configured to receivedemodulation reference signal DMRS indication information, where theDMRS indication information is used to indicate a resource that is notoccupied by DMRS and that is in resources available for carrying a DMRS;and a processor, configured to demodulate, based on the DMRS indicationinformation, data on the resource that is not occupied by DMRS.

When being applied to an uplink transmission scenario, the foregoingapparatus may be a terminal. When being applied to a downlinktransmission scenario, the apparatus may be a network side device. Thenetwork side device may be a base station or a control node.

The network side device may include a system and a device for improvinga peer device in a conventional wireless telecommunications system. Sucha senior or next-generation device may be included in an evolvedwireless communications standard (for example, Long Term Evolution(LTE)).

According to another aspect, an embodiment of this application providesa base station. The base station has functions of implementing behaviorof the base station in the foregoing method designs. The functions maybe implemented by hardware, or may be implemented by hardware executingcorresponding software. The hardware or software includes one or moremodules corresponding to the foregoing functions.

In a possible design, a structure of the base station includes aprocessor and a transceiver. The processor is configured to support thebase station in performing a corresponding function in the foregoingmethods. The transceiver is configured to: support the base station incommunicating with a terminal, send, to the terminal, the information orthe signaling in the foregoing methods, and receive information or aninstruction sent by the base station. The base station may furtherinclude a memory. The memory is configured to be coupled to theprocessor. The memory stores a program instruction and data that arenecessary for the base station.

When being applied to an uplink transmission scenario, the foregoingapparatus may be a network device. When being applied to a downlinktransmission scenario, the apparatus may be a terminal. The terminal hasfunctions of implementing behavior of the terminal in the foregoingmethod designs. The functions may be implemented by hardware, and astructure of the terminal includes a transceiver and a processor.Alternatively, the functions may be implemented by hardware executingcorresponding software. The hardware or software includes one or moremodules corresponding to the foregoing functions. The module may besoftware and/or hardware.

According to still another aspect, an embodiment of this applicationfurther provides a processing apparatus, including a processor and aninterface.

The processor is a processor of the foregoing transmit end or of theforegoing receive end.

The processing apparatus may be a chip. The processor may be implementedby hardware or software. When being implemented by hardware, theprocessor may be a logic circuit, an integrated circuit, or the like.When being implemented by software, the processor may be ageneral-purpose processor, and may be implemented by reading softwarecode stored in a memory. The memory may be integrated in the processor,or may exist independently of the processor.

According to yet another aspect, an embodiment of this applicationprovides a communications system. The system includes the base stationand the terminal in the foregoing aspects, and optionally, may furtherinclude the control node in the foregoing embodiments.

According to still another aspect, an embodiment of this applicationprovides a computer storage medium, configured to store a computersoftware instruction used by the foregoing base station. The computerstorage medium includes a program designed for executing the foregoingaspects.

According to still another aspect, an embodiment of this applicationprovides a computer storage medium, configured to store a computersoftware instruction used by the foregoing terminal. The computerstorage medium includes a program designed for executing the foregoingaspects.

According to the demodulation reference signal sending method andapparatus and the demodulation reference signal obtaining method andapparatus provided in this application, a plurality of pieces of DMRSconfiguration information may be matched with a plurality of scenariosin NR, to satisfy a requirement for transmitting more layers of data. Inaddition, the plurality of information tables support switching. Thiscan further reduce indication overheads.

According to another aspect of the embodiments of the present invention,a data sending method is provided. The method is used for sending aplurality of data streams to a receive-end device through a plurality ofdemodulation reference signal DMRS ports, where the plurality of DMRSports belong to at least two port groups, DMRS ports in each port groupsatisfy a quasi co-location QCL relationship, and any DMRS port in eachport group and any DMRS port in any other port group satisfy a non-quasico-location Non-QCL relationship. The plurality of DMRS ports areallocated to at least two transmit-end devices, and DMRS ports allocatedto each transmit-end device belong to a same port group. The methodincludes the following designs.

In a possible design, each transmit-end device maps a codeword to a datastream corresponding to a DMRS port allocated to the transmit-enddevice; and each transmit-end device sends, to the receive-end device,the data stream corresponding to the DMRS port allocated to thetransmit-end device.

In a possible design, the at least two transmit-end devices are at leasttwo antenna panels of a same transmit-end device; the mapping, by eachtransmit-end device, a codeword to a data stream corresponding to a DMRSport allocated to the transmit-end device is specifically: mapping, bythe same transmit-end device for each antenna panel, a codeword to adata stream corresponding to a DMRS port allocated to the antenna panel;and the sending, by each transmit-end device to the receive-end device,the data stream corresponding to the DMRS port allocated to thetransmit-end device is specifically: sending, by each antenna panel tothe receive-end device, the data stream corresponding to the DMRS portallocated to the antenna panel.

In a possible design, before the mapping, by each transmit-end device, acodeword to a data stream corresponding to a DMRS port allocated to thetransmit-end device, the method further includes: sending, by one of theat least two transmit-end devices, indication information to thereceive-end device, where the indication information is used to indicatethe plurality of DMRS ports allocated to the receive-end device.

In a possible design, before the mapping, by each transmit-end device, acodeword to a data stream corresponding to a DMRS port allocated to thetransmit-end device, the method further includes: sending, by the sametransmit-end device, indication information to the receive-end device,where the indication information is used to indicate the plurality ofDMRS ports allocated to the receive-end device.

In various aspects and possible designs of this embodiment of thepresent invention, a quantity of the plurality of data streams (in otherwords, a quantity of the plurality of DMRS ports) is less than or equalto 4, but may not be limited thereto. For example, the technicalsolution provided in this embodiment of the present invention may beapplied to a scenario in which a quantity of data streams is less thanor equal to 4, but is not applied to a scenario in which a quantity ofdata streams is greater than 4. Further, in the scenario in which thequantity of data streams is less than or equal to 4, the technicalsolution provided in this embodiment of the present invention may beapplied to a scenario in which the quantity of data streams is 3 and/or4 (in other words, the quantity of the plurality of data streams is 3and/or 4), but is not applied to a scenario in which the quantity of theplurality of data streams is 4. Certainly, the technical solutionprovided in this embodiment of the present invention may not be limitedto the foregoing scenarios.

According to a second aspect of the embodiments of the presentinvention, a data receiving method is provided. The method includes:receiving a plurality of data streams through a plurality of DMRS ports,where the plurality of DMRS ports belong to at least two port groups,DMRS ports in each port group satisfy a quasi co-location QCLrelationship, and any DMRS port in each port group and any DMRS port inany other port group satisfy a non-quasi co-location Non-QCLrelationship; and restoring, by a receive-end device for each of the atleast two port groups, a codeword based on a data stream correspondingto a DMRS port that is in the plurality of DMRS ports and that is in theport group.

In a possible design, before the receiving a plurality of data streams,the method further includes: receiving indication information, where theindication information is used to indicate the plurality of DMRS ports.

In a possible design, a quantity of the plurality of data streams (inother words, a quantity of the plurality of DMRS ports) is less than orequal to 4, but may not be limited thereto. For example, the technicalsolution provided in this embodiment of the present invention may beapplied to a scenario in which a quantity of data streams is less thanor equal to 4, but is not applied to a scenario in which a quantity ofdata streams is greater than 4. Further, in the scenario in which thequantity of data streams is less than or equal to 4, the technicalsolution provided in this embodiment of the present invention may beapplied to a scenario in which the quantity of data streams is 3 and/or4 (in other words, the quantity of the plurality of data streams is 3and/or 4), but is not applied to a scenario in which the quantity of theplurality of data streams is 4. Certainly, the technical solutionprovided in this embodiment of the present invention may not be limitedto the foregoing scenarios.

According to a third aspect of the embodiments of the present invention,a data receiving method is provided. The method includes: receiving aplurality of data streams through a plurality of DMRS ports, where theplurality of DMRS ports belong to a same port group, and DMRS ports inthe port group satisfy a quasi co-location QCL relationship; andrestoring a codeword based on the plurality of data streams.

In a possible design, before the receiving a plurality of data streams,the method further includes: receiving indication information, where theindication information is used to indicate the plurality of DMRS ports.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

In the foregoing various aspects and possible designs, the indicationinformation is downlink control information DCI.

The data stream is also referred to as a data layer.

According to a fourth aspect of the embodiments of the presentinvention, a transmit-end device is provided. The transmit-end device isconfigured to send, together with at least one other transmit-enddevice, a plurality of data streams to a receive-end device through aplurality of demodulation reference signal DMRS ports, where theplurality of DMRS ports belong to at least two port groups, DMRS portsin each port group satisfy a quasi co-location QCL relationship, and anyDMRS port in each port group and any DMRS port in any other port groupsatisfy a non-quasi co-location Non-QCL relationship. The plurality ofDMRS ports are allocated to the transmit-end device and the at least oneother transmit-end device, DMRS ports allocated to the transmit-enddevice and each of the at least one other transmit-end device belong toa same port group. The transmit-end device includes: a mapping module,configured to map a codeword to a data stream corresponding to a DMRSport allocated to the transmit-end device; and a transmitting module,configured to send, to the receive-end device, the data streamcorresponding to the DMRS port allocated to the transmit-end device.

In a possible design, the transmit-end device and the at least one othertransmit-end device are at least two antenna panels of a sametransmit-end device; the mapping module is disposed in the sametransmit-end device, and the mapping module is specifically configuredto map, for each antenna panel, a codeword to a data streamcorresponding to a DMRS port allocated to the antenna panel; and thetransmitting module is disposed in the same transmit-end device, and thetransmitting module is specifically configured to: send, by each antennapanel to the receive-end device, the data stream corresponding to theDMRS port allocated to the antenna panel.

In a possible design, the transmitting module is further configured tosend indication information to the receive-end device, where theindication information is used to indicate the plurality of DMRS portsallocated to the receive-end device.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

According to a fifth aspect of the embodiments of the present invention,a receive-end device is provided. The receive-end device includes: areceiving module, configured to receive a plurality of data streamsthrough a plurality of DMRS ports, where the plurality of DMRS portsbelong to at least two port groups, DMRS ports in each port groupsatisfy a quasi co-location QCL relationship, and any DMRS port in eachport group and any DMRS port in any other port group satisfy a non-quasico-location Non-QCL relationship; and a restoration module, configuredto restore, for each of the at least two port groups, a codeword basedon a data stream corresponding to a DMRS port that is in the pluralityof DMRS ports and that is in the port group.

In a possible design, the receiving module is further configured toreceive indication information, where the indication information is usedto indicate the plurality of DMRS ports.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

According to a sixth aspect of the embodiments of the present invention,a receive-end device is provided. The receive-end device includes: areceiving module, configured to receive a plurality of data streamsthrough a plurality of DMRS ports, where the plurality of DMRS portsbelong to a same port group, and DMRS ports in the port group satisfy aquasi co-location QCL relationship; and a restoration module, configuredto restore a codeword based on the plurality of data streams.

In a possible design, the receiving module is further configured toreceive indication information, where the indication information is usedto indicate the plurality of DMRS ports.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

In the foregoing various aspects and designs of this embodiment of thepresent invention, the indication information may be downlink controlinformation DCI.

According to a seventh aspect of the embodiments of the presentinvention, a data sending method is provided. The method is used forsending a plurality of data streams to a receive-end device through aplurality of demodulation reference signal DMRS ports, where theplurality of DMRS ports belong to at least two port groups, DMRS portsin each port group satisfy a quasi co-location QCL relationship, and anyDMRS port in each port group and any DMRS port in any other port groupsatisfy a non-quasi co-location Non-QCL relationship. The plurality ofDMRS ports are allocated to a same transmit-end device. For each portgroup, the method includes: mapping, by the transmit-end device, acodeword to a data stream corresponding to a DMRS port that is in theplurality of DMRS ports and that is in the port group; and sending, bythe transmit-end device, the data stream to the receive-end device.

In a possible design, the method further includes: sending, by thetransmit-end device, indication information to the receive-end device,where the indication information is used to indicate the plurality ofDMRS ports allocated to the receive-end device.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

According to an eighth aspect of the embodiments of the presentinvention, a transmit-end device is provided. The transmit-end device isconfigured to send a plurality of data streams to a receive-end devicethrough a plurality of demodulation reference signal DMRS ports, wherethe plurality of DMRS ports belong to at least two port groups, DMRSports in each port group satisfy a quasi co-location QCL relationship,and any DMRS port in each port group and any DMRS port in any other portgroup satisfy a non-quasi co-location Non-QCL relationship. Theplurality of DMRS ports are allocated to the transmit-end device. Thetransmit-end device includes: a mapping module, configured to map, foreach port group, a codeword to a data stream corresponding to a DMRSport that is in the plurality of DMRS ports and that is in the portgroup; and a transmitting module, configured to send the data stream tothe receive-end device.

In a possible design, the method further includes: the transmittingmodule is further configured to send indication information to thereceive-end device, where the indication information is used to indicatethe plurality of DMRS ports allocated to the receive-end device.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

To sum up, the embodiments of the present invention provide a datasending method. The method is used for sending a plurality of datastreams to a receive-end device through a plurality of demodulationreference signal DMRS ports, where the plurality of DMRS ports belong toat least two port groups, DMRS ports in each port group satisfy a quasico-location QCL relationship, and any DMRS port in each port group andany DMRS port in any other port group satisfy a non-quasi co-locationNon-QCL relationship. For each port group, the method includes: mappinga codeword to a data stream corresponding to a DMRS port that is in theplurality of DMRS ports and that is in the port group; and sending thedata stream to the receive-end device.

In a possible design, the method further includes: sending indicationinformation to the receive-end device, where the indication informationis used to indicate the plurality of DMRS ports allocated to thereceive-end device.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

In a possible design, the plurality of DMRS ports may be allocated to asame transmit-end device; or may be allocated to a plurality of antennapanels of a same transmit-end device, where DMRS ports allocated to eachantenna panel belong to a same port group; or may be allocated to aplurality of transmit-end devices serving a same receive-end device (forexample, based on a coordinated multi-point (CoMP) related technology),where DMRS ports allocated to each transmit-end device belong to a sameport group. In addition, the DMRS ports may alternatively be allocatedto one or more transmit-end devices in another manner, for example, butnot limited to, various feasible combinations of the foregoing severalmanners.

Correspondingly, an embodiment of the present invention further providesa data receiving method, including: receiving a plurality of datastreams through a plurality of DMRS ports, where the plurality of DMRSports belong to a same port group or at least two port groups, DMRSports in each port group satisfy a quasi co-location QCL relationship,and any DMRS port in each port group and any DMRS port in any other portgroup satisfy a non-quasi co-location Non-QCL relationship; andrestoring, by a receive-end device for the same port group or each ofthe at least two port groups, a codeword based on a data streamcorresponding to a DMRS port that is in the plurality of DMRS ports andthat is in the port group.

In a possible design, before the receiving a plurality of data streams,the method further includes: receiving indication information, where theindication information is used to indicate the plurality of DMRS ports.

A quantity of the plurality of data streams is less than or equal to 4.

It is easily understood that, on a side of the receive-end device, thereceive-end device may not need to be concerned about whether theplurality of DMRS ports come from a same transmit-end device, aplurality of antenna panels of a same transmit-end device, or aplurality of transmit-end devices.

Quasi co-location (QCL) is usually used to describe similar large-scalefading, similar spatial directions (for example, but not limited to,beam directions), and the like. Therefore, non-quasi co-location(Non-QCL) is usually used to describe different large-scale fading,different spatial directions, and the like. Related content of the QCLand the non-QCL has been clearly described in the prior art, andtherefore, is not described herein.

During actual transmission, an information bit is usually divided in aform of a transport block (Transport Block, TB), and a transport blockmay be a codeword (CW). For content related to the TB and the CW, referto the prior art.

Usually, DMRS ports supported by a system may be grouped into aplurality of port groups, DMRS ports in each port group satisfy a QCLrelationship, and any DMRS port in each port group and any DMRS port inany other port group satisfy a non-QCL relationship. When a plurality oftransmit-end devices serve a same receive-end device, DMRS portsallocated to each transmit-end device come from a same port group. Forexample, DMRS ports 0 to 9 may be grouped into two port groups, namely,a port group 1 and a port group 2, where the DMRS ports 0 to 4 belong tothe port group 1, and the DMRS ports 5 to 9 belong to the port group 2.When DMRS ports are allocated to a transmit-end device, any quantity ofDMRS ports in the port group 1 may be allocated to the transmit-enddevice, or any quantity of DMRS ports in the port group 2 may beallocated to the transmit-end device. In addition, regardless of whethera receive-end device is served by a plurality of transmit-end devices ora single transmit-end device, DMRS ports allocated to a sametransmit-end device may come from a same port group or from differentport groups. For example, when the DMRS ports come from a same portgroup, the port 1 and the port 2 in the port group 1 may be allocated tothe transmit-end device. When the DMRS ports come from different portgroups, the ports 2 and 3 in the port group 1 and the ports 8 and 9 inthe port group 2 may be allocated to the transmit-end device. It iseasily understood that, when DMRS ports allocated to a same transmit-enddevice come from different port groups, wireless transmission performedby the transmit-end device through the DMRS ports in the different portgroups has a non-QCL characteristic, for example, has differentlarge-scale fading, different spatial directions, or the like. When DMRSports allocated to a same transmit-end device come from a same portgroup, wireless transmission performed by the transmit-end devicethrough the DMRS ports in the same port group has a QCL characteristic,for example, has similar large-scale fading, similar spatial directions,or the like.

For related content of grouping DMRS ports into a plurality of portgroups, refer to the prior art. For example, a grouping status of DMRSports may be preset in the transmit-end device and the receive-enddevice before delivery, or the transmit-end device may notify thereceive-end device of a grouping status of DMRS ports. For example, butnot limited to that, the transmit-end device notifies the receive-enddevice of the grouping status by using an Radio Resource Control (RRC)message, for example, but not limited to, periodically or when thereceive-end device accesses a communications network. When DMRS portsare grouped into a plurality of port groups, a DMRS port may beallocated to the transmit-end device based on a grouping status and aspecific requirement (for example, various application scenarios, suchas CoMP).

The plurality of transmit-end devices may be a plurality of transmit-enddevices, or may be a plurality of antenna panels of a same transmit-enddevice. The transmit-end device may be, for example, but not limited to,a base station. The receive-end device may be, for example, but notlimited to, a terminal.

For the process of mapping the codeword to the data stream and theprocess of restoring the codeword from the data stream, refer to theprior art.

When the plurality of transmit-end devices serve a same receive-enddevice, the indication information may be sent by one of the pluralityof transmit-end devices. In this case, the transmit-end device sendingthe indication information may be referred to as a serving device, andother transmit-end devices may be referred to as coordinating devices.

The data stream may also be referred to as a data layer, and usually,may be obtained by performing layer mapping on a codeword. For aspecific process, refer to the prior art.

The steps in the foregoing method may be performed by one or moreprocessors, or may be performed by one or more processors executing aprogram.

Functions of the modules of the transmit-end device and the receive-enddevice may be performed by one or more processors, or may be performedby one or more processors executing a program.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of thisapplication more clearly, the following briefly describes theaccompanying drawings required for describing the embodiments.Apparently, the accompanying drawings in the following description showmerely some embodiments of this application, and a person of ordinaryskill in the art may derive other drawings from these accompanyingdrawings without creative efforts.

FIG. 1 is a schematic diagram of a pilot pattern in the prior art;

FIG. 2 is a schematic diagram of a resource unit according to anembodiment of this application;

FIG. 3 is a schematic diagram of a system architecture to which thetechnical solutions provided in the embodiments of this application areapplicable;

FIG. 4 is a schematic structural diagram of a base station according toan embodiment of this application;

FIG. 5 is a schematic structural diagram of a terminal according to anembodiment of this application;

FIG. 6 is a schematic interaction diagram of a DMRS indicating andreceiving method according to an embodiment of this application;

FIG. 7 is a schematic diagram of a DMRS pattern according to anembodiment of this application;

FIG. 8 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 9 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 10 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 11 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 12 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 13 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 14 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 15 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 16 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 17 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 18 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 19 is a schematic diagram of another DMRS pattern according to anembodiment of this application;

FIG. 20 is a schematic diagram of an MU-MIMO scenario in an LTE system;

FIG. 21 is another schematic interaction flowchart of a DMRS indicatingand receiving method according to an embodiment of this application;

FIG. 22 is a schematic scenario diagram of a DMRS indicating andreceiving method according to an embodiment of this application;

FIG. 23 is a schematic diagram of a correspondence between indicationinformation and a pattern in a DMRS indicating and receiving methodaccording to an embodiment of this application;

FIG. 24 is another schematic scenario diagram of a DMRS indicating andreceiving method according to an embodiment of this application;

FIG. 25 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 26 is another schematic scenario diagram of a DMRS indicating andreceiving method according to an embodiment of this application;

FIG. 27 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 28 is another schematic scenario diagram of a DMRS indicating andreceiving method according to an embodiment of this application;

FIG. 29 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 30 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 31 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 32 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 33 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 34 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 35 is another schematic application scenario diagram of a DMRSindicating and receiving method according to an embodiment of thisapplication;

FIG. 36 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 37 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 38 is a schematic scenario diagram of a DMRS indicating andreceiving method according to an embodiment of this application;

FIG. 39 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 40 is another schematic diagram of a correspondence betweenindication information and a pattern in a DMRS indicating and receivingmethod according to an embodiment of this application;

FIG. 41 is a schematic block diagram of a transmit end according to anembodiment of this application;

FIG. 42 is a schematic block diagram of a receive end according to anembodiment of this application; and

FIG. 43 is a schematic diagram of a transmit end or a receive endaccording to an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

First, to facilitate understanding by readers, related terms in thisspecification are briefly described.

(1) Resource Unit

Similar to an RB and an RB pair in an LTE standard, a resource unit isprovided in some embodiments of this application. The resource unit maybe used as a basic unit for scheduling a terminal to allocate aresource, or may be used to describe a manner of arranging a pluralityof reference signals.

The resource unit may include a plurality of consecutive subcarriers infrequency domain and a time interval (TI) in time domain. In differentscheduling processes, sizes of a resource unit may be the same ordifferent. The TI herein may be a transmission time interval (TTI) in anLTE system, a symbol-level short TTI, a short TTI in a large subcarrierspacing in a high-frequency system, a slot or a mini-slot in a 5Gsystem, or the like. This is not limited in this application.

Optionally, one resource unit may include one or more RBs, one or moreRB pairs, or the like, or may be half an RB or the like. In addition,the resource unit may be another time-frequency resource. This is notlimited in this application. One RB pair includes 12 consecutivesubcarriers in frequency domain and a subframe in time domain. Atime-frequency resource including one subcarrier in frequency domain andone symbol in time domain is a resource element (RE), as shown in FIG.2. An RB pair in FIG. 2 includes 12 consecutive subcarriers (numberedfrom 0 to 11) in frequency domain and 14 symbols (numbered from 0 to 13)in time domain. In FIG. 2, a horizontal coordinate indicates the timedomain, and a vertical coordinate indicates the frequency domain. Itshould be noted that all accompanying drawings indicating a time domainresource in this application are described based on an example of the RBpair shown in FIG. 2. A person skilled in the art may understand thatspecific implementation is not limited thereto. It may be understoodthat, the “symbol” in this application may include but is not limited toany one of the following: an orthogonal frequency division multiplexing(OFDM) symbol, a universal filtered multi-carrier (UFMC) signal, afilter-band multi-carrier (FBMC) symbol, a generalizedfrequency-division multiplexing (GFDM) symbol, and the like.

(2) DMRS Port Group

The “DMRS port group” used in this application is a logical conceptintroduced to clearly describe technical solutions provided in thisapplication, and specifically, is a logical concept introduced toclearly describe a pilot pattern or a variant thereof provided in thisapplication. It may be understood that, during actual implementation, abase station and a terminal may not group DMRS ports, and a pilotpattern or a variant thereof designed in any manner and described inthis application shall fall within the protection scope of thisapplication.

One DMRS port group may include one or more DMRS ports. In thisapplication, a same time-frequency resource is multiplexed for DMRSscorresponding to ports in a DMRS port group through CDM, for example,orthogonal cover code (OCC), cyclic shift (CS), cyclic phase rotation,or a combination of a plurality of the foregoing methods, for example,OCC+CS. A technical solution in which a time-frequency resource ismultiplexed for a plurality of reference signals through CDM has beenclearly described in the prior art, and details are not described inthis specification.

(3) System-Supported DMRS Port

A system-supported DMRS port may be considered as a DMRS port that canbe used by the base station. During actual implementation, the basestation may schedule a terminal by using some or all of DMRS portsupported by the base station. A maximum supported orthogonal-portquantity is a maximum value of a quantity of orthogonal DMRS ports thatcan be supported by the system or the base station.

In this application, that a quantity of system-supported DMRS ports is4, 6, 8, and 12 is used as an example for description.

(4) Other Terms

“A plurality of” in this specification indicates two or more than two.

Terms “first” and “second” in this specification are only intended todistinguish between different objects, but do not limit a sequence ofthe objects. For example, a first symbol group and a second symbol groupare only intended to distinguish between different symbol groups, but donot limit a sequence.

The term “and/or” in this specification describes only an associationrelationship for describing associated objects and represents that threerelationships may exist. For example, A and/or B may represent thefollowing three cases: Only A exists, both A and B exist, and only Bexists. In addition, the character “/” in this specification generallyindicates an “or” relationship between associated objects.

The following describes the technical solutions provided in thisapplication with reference to the accompanying drawings.

The technical solutions provided in this application may be applied tovarious communications systems, for example, current 2G, 3G, and 4Gcommunications systems, and future evolved networks such as a 5Gcommunications system, for example, an LTE system, a 3rd GenerationPartnership Project (3GPP) related cellular system, and othercommunications systems of this type, and particularly, may be applied toa 5G NR system.

It should be noted that a 5G standard may include a machine to machine(machine to machine, M2M) scenario, a device to machine (D2M) scenario,a macro/micro communication scenario, an enhanced mobile broadband(eMBB) scenario, an ultra-reliable and low latency communication (uRLLC)scenario, a massive machine type communication (mMTC) scenario, and thelike. These scenarios may include but are not limited to a communicationscenario between terminals, a communication scenario between basestations, a communication scenario between a base station and aterminal, and the like. The technical solutions provided in theembodiments of this application may also be applied to scenarios such ascommunication between terminals or communication between base stationsin the 5G communications system.

The technical solutions provided in the embodiments of this applicationmay be applied to a system architecture shown in FIG. 3. The systemarchitecture may include a base station 100 and one or more terminals200 connected to the base station 100.

In an example, the base station 100 may be implemented by using astructure shown in FIG. 4.

The base station 100 may be a device capable of communicating with theterminal 200. The base station 100 may be a relay station, an accesspoint, or the like. The base station 100 may be a base transceiverstation (BTS) in a Global System for Mobile Communications (GSM) or in aCode Division Multiple Access (CDMA) network, or may be an NB (NodeB) inWideband Code Division Multiple Access (WCDMA), or may be an eNB oreNodeB (evolvedNodeB) in LTE. Alternatively, the base station 100 may bea wireless controller in a cloud radio access network (CRAN) scenario.Alternatively, the base station 100 may be a network device in a 5Gnetwork or a network device in a future evolved PLMN network, or may bea wearable device, an in-vehicle device, or the like.

The terminal 200 may be user equipment (UE), an access terminal, a UEunit, a UE station, a mobile station, a mobile console, a remotestation, a remote terminal, a mobile device, a UE terminal, a wirelesscommunications device, a UE agent, a UE apparatus, or the like. Theaccess terminal may be a cellular phone, a cordless phone, a SessionInitiation Protocol (SIP) phone, a wireless local loop (WLL) station, apersonal digital assistant (PDA), a handheld device having a wirelesscommunication function, a computing device, another processing deviceconnected to a wireless modem, an in-vehicle device, a wearable device,a terminal in a future 5G network, or a terminal in a future evolvedPLMN network, or the like.

A universal hardware architecture of the base station 100 is described.As shown in FIG. 4, the base station may include a building basebandunit (BBU) and a remote radio unit (RRU). The RRU is connected to anantenna feed system (in other words, an antenna), and the BBU and theRRU may be disassembled for use based on a requirement. It should benoted that, in a specific implementation process, the base station 100may further use another universal hardware architecture, and is notlimited to the universal hardware architecture shown in FIG. 4.

That the terminal 200 is a mobile phone is used as an example todescribe a universal hardware architecture of the mobile phone. As shownin FIG. 5, the mobile phone includes components such as a radiofrequency (RF) circuit 110, a memory 120, another input device 130, adisplay screen 140, a sensor 150, an audio circuit 160, an I/O subsystem170, a processor 180, and a power supply 190. A person skilled in theart may understand that the structure of the mobile phone shown in FIG.5 does not constitute a limitation on the mobile phone, and the mobilephone may include more or fewer components than those shown in thefigure, or some components may be combined, some components may bedisassembled, or different component arrangements may be used. A personskilled in the art may understand that the display screen 140 belongs toa user interface (UI), and the display screen 140 may include a displaypanel 141 and a touch panel 142. In addition, the mobile phone mayinclude more or fewer components than those shown in the figure.Although not shown, the mobile phone may further include functionalmodules or parts such as a camera and a Bluetooth module, and detailsare not described herein.

Further, the processor 180 is connected to all of the RF circuit 110,the memory 120, the audio circuit 160, the I/O subsystem 170, and thepower supply 190. The I/O sub-system 170 is connected to all of theanother input device 130, the display screen 140, and the sensor 150.The RF circuit 110 may be configured to send and receive signals in aninformation sending and receiving process or a call process.Particularly, the RF circuit receives downlink information from a basestation, and then delivers the downlink information to the processor 180for processing. The memory 120 may be configured to store a softwareprogram and module. The processor 180 runs the software program andmodule that are stored in the memory 120, to perform various functionalapplications of the mobile phone and process data. The another inputdevice 130 may be configured to: receive input digit or characterinformation, and generate a key signal input related to a user settingand function control of the mobile phone. The display screen 140 may beconfigured to display information entered by a user or informationprovided for a user and various menus on the mobile phone, and mayfurther receive a user input. The sensor 150 may be an optical sensor, amotion sensor, or another sensor. The audio circuit 160 may provide anaudio interface between a user and the mobile phone. The I/O subsystem170 is configured to control an external input/output device, and theexternal device may include another device input controller, a sensorcontroller, and a display controller. The processor 180 is a controlcenter of the mobile phone 200, and is connected to various parts of theentire mobile phone by using various interfaces and lines. By running orexecuting the software program and/or module stored in the memory 120,and scheduling the data stored in the memory 120, the processor 180performs various functions of the mobile phone 200 and processes data,thereby performing overall monitoring on the mobile phone. The powersupply 190 (such as a battery) is configured to supply power to thecomponents. Preferably, the power supply may be logically connected tothe processor 180 by using a power supply management system, so as toimplement functions such as charging, discharging, and power consumptionmanagement by using the power supply management system.

The technical solutions provided in this application may be applied to asingle-carrier transmission scenario, a multi-carrier transmissionscenario, a scenario in which a plurality of waveforms are mixedlytransmitted, an uplink transmission scenario, a downlink transmissionscenario, or a scenario with both uplink and downlink transmission.

The following describes a DMRS transmission method provided in thisapplication. The DMRS transmission method may include a method forsending a DMRS by a transmit end and a method for obtaining the DMRS bya receive end.

FIG. 6 shows a DMRS transmission method provided in this application.The method may include the following steps.

S101. A transmit end determines, from a plurality of groups ofdemodulation reference signal DMRS configuration information, DMRSconfiguration information corresponding to a current DMRS transmissionscheme, and obtains DMRS indication information based on the DMRSconfiguration information, where each group of DMRS configurationinformation includes a plurality of pieces of DMRS configurationinformation.

The plurality of pieces of DMRS configuration information may bepresented in a form of a DMRS configuration information table. In onemanner, the plurality of pieces of DMRS configuration information arepresented in a form of a plurality of independent tables. Or theplurality of pieces of DMRS configuration information are subsets of ageneral information table.

S102. The transmit end sends the DMRS indication information on atime-frequency resource.

S103. A receive end receives the DMRS indication information.

S104. The receive end performs channel estimation or assists indemodulating data, based on the received DMRS indication information.

A time-frequency resource used to carry a DMRS may include one or moresymbols in time domain, and may include one or more subcarriers infrequency domain.

If the technical solution is applied to an uplink transmission scenario,the transmit end may be a terminal, and the receive end may be a basestation. If the technical solution is applied to a downlink transmissionscenario, the transmit end may be a base station, and the receive endmay be a terminal.

In this embodiment of this application, the current DMRS transmissionscheme is indicated by using the indication information, and differentDMRS transmission schemes correspond to different maximum supportedorthogonal-port quantities, or correspond to different DMRS patterns ordifferent DMRS configuration types.

The maximum supported orthogonal-port quantities in DMRS configurationinformation corresponding to the different DMRS transmission schemes aredifferent.

Lengths of DMRS indication information corresponding to the differentDMRS transmission schemes are different.

A plurality of DMRS ports in the at least one piece of DMRSconfiguration information belong to different code division multiplexingCDM groups, where different CDM groups satisfy a non-quasi co-locationQCL relationship.

For different maximum supported orthogonal-port quantities, differentDMRS configuration information may be configured. For example, in MIMOscenarios in which a maximum supported orthogonal-port quantity is 4, amaximum supported orthogonal-port quantity is 6, a maximum supportedorthogonal-port quantity is 8, and a maximum supported orthogonal-portquantity is 12, corresponding DMRS configuration information isseparately configured. The DMRS configuration information is used toinform the receive end of an orthogonal DMRS port number, a sequenceconfiguration, a multiplexing mode, and the like that can be used by thereceive end, thereby correctly decoding data.

In another implementation, the DMRS configuration information isconfigured for different DMRS patterns. Usually, one DMRS patterncorresponds to one MIMO scenario that supports a maximum supportedorthogonal-port quantity or a maximum supportedorthogonal-transmission-layer quantity. The DMRS pattern shows aquantity of orthogonal port groups supported by the MIMO scenario and aquantity of resource units included in each orthogonal port group.Therefore, configuring different DMRS configuration information fordifferent DMRS patterns can also enable the receive end to know anorthogonal DMRS port number, a sequence configuration, a multiplexingmode, and the like that can be used by the receive end, therebycorrectly decoding data.

In an implementation, the DMRS configuration information may bepresented by a protocol-agreed table, and a specific implementation formthereof may be a downlink control information (DCI) table. A pluralityof DCI tables include at least one group of different DMRS configurationinformation. The DMRS transmission scheme corresponding to the DMRSconfiguration information is sent by using higher layer signaling, forexample, radio resource control (RRC) signaling. Certainly, the DMRSconfiguration information may alternatively be bound with anotherconfiguration parameter, for example, a frequency, a carrier spacing, ora frame structure, corresponding to a scenario. In this way, the DMRSindication information can be sent by using DCI signaling or a mediaaccess control control element (MAC CE).

During specific implementation, each DMRS configuration informationtable corresponds to a different maximum supported orthogonal-portquantity (port). For example, the maximum supported orthogonal-portquantity may be at least two of {4, 6, 8, 12}.

In another implementation, each DMRS configuration information table maycorrespond to a different DMRS pattern or DMRS configuration type.

In an implementation, in the information table, column arrangementdesign is performed based on an orthogonal port combination. Forexample, column arrangement design is performed on an orthogonal portcombination having four or less transmission layers and an orthogonalport combination having more than four transmission layers.

In an implementation, when the DMRS configuration information ispresented in a form of a DMRS configuration information table, divisionmay be performed based on a codeword number codeword number, or may beperformed based on a total maximum supported orthogonal-port quantity ora quantity of transmission layers at the receive end, instead of acodeword number. Specifically, division may be performed based on aratio.

The DMRS configuration information further includes indicationinformation of a total quantity of orthogonal ports, and the indicationinformation may indicate a quantity of all orthogonal ports that arepossibly actually presented or a quantized value of a quantity of allorthogonal ports that are possibly actually presented. The quantizedvalue of the quantity of all the orthogonal ports may be informationabout a quantity of orthogonal DMRS layers, indication information of anorthogonal DMRS antenna port set, CDM group information of an orthogonalDMRS antenna port, or information generated based on a CDM group size.It should be understood that the total quantity of orthogonal ports isthe same as a total quantity of orthogonal DMRS transmission layers.

A reason for using a quantized value of a quantity of orthogonal DMRStransmission layers is that if a specific quantity of transmissionlayers of the receive end needs to be indicated, for example, iforthogonal-transmission-layer quantities {1, 2, 3, 4} need to beindicated, four bits are required for indication. When theorthogonal-transmission-layer quantities {1, 2, 3, 4} are quantized intoa value, for example, quantized upward into anorthogonal-transmission-layer quantity 4, or quantized downward into anorthogonal-transmission-layer quantity 1, or when theorthogonal-transmission-layer quantities {1, 2, 3, 4} are represented by2 or 3, only one bit is required to indicate the quantized value of thequantity of orthogonal transmission layers. For example, 0 is used torepresent a quantized value 4 of the orthogonal-transmission-layerquantity. Therefore, indication overheads can be reduced.

It should be noted that, a plurality of DMRS configuration informationtables may alternatively be a general information table, the generalinformation table supports a maximum supported port quantity, and theplurality of DMRS configuration information tables are subsets of thegeneral information table. A subset may be selected from the generalinformation table based on the maximum supported port quantity, the DMRSpattern, or the higher layer signaling.

The following describes specific implementation processes of sending aDMRS and obtaining a DMRS that are provided in this application.

Embodiment 1

A plurality of tables of DMRS configuration information, brieflyreferred to as DMRS configuration information tables, are designed inEmbodiment 1. Each DMRS configuration information table is associatedwith a maximum supported orthogonal-port quantity, or different DMRSconfiguration information tables are designed for different DMRSpatterns or different DMRS configuration types. Each of the maximumsupported orthogonal-port quantity, the DMRS pattern, and the DMRSconfiguration type can indicate a DMRS transmission scheme. Beforetransmission, based on different pattern configuration information, aDMRS configuration information table is selected or switching isperformed between different DMRS configuration information tables.

As shown in FIG. 7, the DMRS configuration information table is a DMRSconfiguration information table designed based on a maximum supportedorthogonal-port quantity of a single terminal (UE) being 4 in SU-MIMO orMU-MIMO.

TABLE 1 DMRS for a maximum of four ports One Codeword (≤4 layers): TwoCodewords (>4 layers): Codeword 0 enabled, Codeword 0 enabled, Codeword1 disabled Codeword 1 enabled Value UE rank Port index Value UE rankPort index 1 1 layer, port 0 0 Reserved Reserved 1 1 layer, port 1 1Reserved Reserved 1 1 layer, port 2 2 Reserved Reserved 1 1 layer, port3 3 Reserved Reserved 2 2 layers, ports 0-1 4 Reserved Reserved 2 2layers, ports 2-3 5 Reserved Reserved 3 3 layers, ports 0-2 6 ReservedReserved 4 4 layers, ports 0-3 7 Reserved Reserved Reserve Reserve 8Reserved Reserved

DMRS indication information or an index is represented by using a value.When the value is 0, it indicates that the terminal supports onetransmission layer (which is represented by a rank in the table), and anorthogonal port index corresponding to the value 0 is one transmissionlayer with a port number of 0. For another example, when the value ofthe DMRS indication information is 7, it indicates that the terminalsupports four transmission layers (Rank), and orthogonal port indexescorresponding to the value 7 are 0 to 3 (ports 0 to 3).

A port combination shown in Table 1 may basically cover allconfigurations of four or less ports, where reserved may be used for anadditional combination (combination) to increase scheduling flexibility,although the listed combinations have satisfied a schedulingrequirement.

The DMRS configuration information table shown in Table 1 is applicableto an orthogonal DMRS implementing a maximum of four streams/layers ofdata transmission or a pattern corresponding to FIG. 7 (for example,config. 1-1 symbol in a left part or config. 1-2 symbols in a rightpart, but time-domain repetition is used, e.g., TD-OCC {(1, 1), (1,1)}).

The DMRS configuration information table in this embodiment is designedbased on an LTE table (in other words, columns are divided based on acodeword number), and a corresponding value requires three bits ofindication overheads.

It should be understood that, the port index in the DMRS configurationinformation table is only a representation manner, and is only anexample for description. Alternatively, another digit may be used forindication based on an actual requirement.

As shown in FIG. 2, the DMRS configuration information table is a DMRSconfiguration information table designed based on a maximum supportedorthogonal-port quantity of a single terminal (UE) being 6 in SU-MIMO orMU-MIMO.

TABLE 2 DMRS for a maximum of six ports One Codeword (≤4 layers): TwoCodewords (>4 layers): Codeword 0 enabled, Codeword 0 enabled, Codeword1 disabled Codeword 1 enabled Value UE rank Port index Value UE rankPort index 0 1 0 0 5 0-4 (SU) 1 1 1 1 6 0-5 (SU) 2 1 2 2 ReservedReserved 3 1 3 3 Reserved Reserved 4 1 4 4 Reserved Reserved 5 1 5 5Reserved Reserved 6 2 0-1 6 Reserved Reserved 7 2 2-3 7 ReservedReserved 8 2 4-5 8 Reserved Reserved 9 3 0-2 9 Reserved Reserved 10 33-5 10 Reserved Reserved 11 4 0-3 11 Reserved Reserved 12 ReservedReserved 12 Reserved Reserved 13 Reserved Reserved 13 Reserved Reserved14 Reserved Reserved 14 Reserved Reserved 15 Reserved Reserved 15Reserved Reserved 16 Reserved Reserved 16 Reserved Reserved

Indication information or an index of DMRS configuration information isrepresented by using a value. For example, when the value of theindication information of the DMRS configuration information is 0, itindicates that the terminal supports one transmission layer (Rank), andan orthogonal port index corresponding to the value 0 is 0. When thevalue of the indication information of the DMRS configurationinformation is 10, it indicates that the terminal supports threetransmission layers (Rank), and orthogonal port indexes corresponding tothe value 10 are 3 to 5. It should be noted that the orthogonal portindex herein is only an example, and a specific orthogonal port numbermay be represented by using another digit.

A port combination listed in a table shown in Table 2 may basicallycover all configurations of six or less ports, where reserved may beused for an additional combination to increase scheduling flexibility,although the listed combinations have satisfied a schedulingrequirement.

The DMRS configuration information table shown in Table 2 is applicableto an orthogonal DMRS implementing a maximum of six streams/layers ofdata transmission or a pattern corresponding to FIG. 8 (for example,config. 1-1 symbol in a left part or config. 1-2 symbol in a right part,but time-domain repetition is used, e.g., TD-OCC {(1, 1), (1, 1)}).

The DMRS configuration information table in this embodiment is designedbased on an LTE table (in other words, columns are divided based on acodeword number), and a corresponding value requires four bits ofindication overheads.

As shown in FIG. 3, the DMRS configuration information table is a DMRSconfiguration information table designed based on a maximum supportedorthogonal-port quantity of a single terminal (UE) being 8 in SU-MIMO orMU-MIMO.

TABLE 3 DMRS for a maximum of eight ports One Codeword (≤4 layers): TwoCodewords (>4 layers): Codeword 0 enabled, Codeword 0 enabled, Codeword1 disabled Codeword 1 enabled Value UE rank Port index Value UE rankPort index 0 1 0 0 5 0-4 1 1 1 1 6 0-5 2 1 2 2 7 0-6 3 1 3 3 8 0-7 4 1 44 Reserved Reserved 5 1 5 5 Reserved Reserved 6 1 6 6 Reserved Reserved7 1 7 7 Reserved Reserved 8 2 0-1 8 Reserved Reserved 9 2 2-3 9 ReservedReserved 10 2 4-5 10 Reserved Reserved 11 2 6-7 11 Reserved Reserved 123 0-2 12 Reserved Reserved 13 3 3-5 13 Reserved Reserved 14 4 0-3 14Reserved Reserved 15 4 4-7 15 Reserved Reserved

Indication information of DMRS configuration information is representedby using a value. For example, when the value of the indicationinformation of the DMRS configuration information is 0, it indicatesthat the terminal supports one transmission layer (Rank), and anorthogonal port index corresponding to the value 0 is 0. For anotherexample, when the value is 15, it indicates that the terminal supportsfour transmission layers (Rank), and orthogonal port indexescorresponding to the value 15 are 4 to 7. It should be noted that theorthogonal port index herein is only an example, and a specificorthogonal port number may be represented by using another digit.

A port combination listed in a table shown in Table 3 may basicallycover all configurations of eight or less ports, where reserved may beused for an additional combination (combination) to increase schedulingflexibility, although the listed combinations have satisfied ascheduling requirement.

The DMRS configuration information table shown in Table 3 is applicableto an orthogonal DMRS implementing a maximum of eight streams/layers ofdata transmission or a pattern corresponding to FIG. 9 (config. 1-2symbols).

The DMRS configuration information table in this embodiment is designedbased on an LTE table (in other words, columns are divided based on acodeword number), and a corresponding value requires four bits ofindication overheads.

As shown in FIG. 4, the DMRS configuration information table is a DMRSconfiguration information table designed based on a maximum supportedorthogonal-port quantity of a single terminal (UE) being 12 in SU-MIMOor MU-MIMO.

TABLE 4 DMRS for a maximum of 12 ports One Codeword (≤4 layers): TwoCodewords (>4 layers): Codeword 0 enabled, Codeword 0 enabled, Codeword1 disabled Codeword 1 enabled Value UE rank Port index Value UE rankPort index 0 1 0 0 5 0-4 1 1 1 1 6 0-5 2 1 2 2 7 0-6 3 1 3 3 8 0-7 4 1 44 Reserved Reserved 5 1 5 5 Reserved Reserved 6 1 6 6 Reserved Reserved7 1 7 7 Reserved Reserved 8 1 8 8 Reserved Reserved 9 1 9 9 ReservedReserved 10 1 10 10 Reserved Reserved 11 1 11 11 Reserved Reserved 12 20-1 12 Reserved Reserved 13 2 2-3 13 Reserved Reserved 14 2 4-5 14Reserved Reserved 15 2 6-7 15 Reserved Reserved 16 2 8-9 16 ReservedReserved 17 2 10-11 17 Reserved Reserved 18 3 0-2 18 Reserved Reserved19 3 3-5 19 Reserved Reserved 20 3 6-8 20 Reserved Reserved 21 3  9-1121 Reserved Reserved 22 4 0-3 22 Reserved Reserved 23 4 4-7 23 ReservedReserved 24 4  8-11 24 Reserved Reserved 25 Reserve Reserve 25 ReservedReserved 26 Reserve Reserve 26 Reserved Reserved 27 Reserve Reserve 27Reserved Reserved 28 Reserve Reserve 28 Reserved Reserved 29 ReserveReserve 29 Reserved Reserved 30 Reserve Reserve 30 Reserved Reserved 31Reserve Reserve 31 Reserved Reserved

Indication information of DMRS configuration information is representedby using a value. For example, when the value of the indicationinformation of the DMRS configuration information is 0, it indicatesthat the terminal supports one transmission layer (Rank), and anorthogonal port index corresponding to the value 0 is 0. For anotherexample, when the value of the indication information of the DMRSconfiguration information is 24, it indicates that the terminal supportsfour transmission layers (Rank), and orthogonal port indexescorresponding to the value 24 are 8 to 11. It should be noted that theorthogonal port index herein is only an example, and a specificorthogonal port number may be represented by using another digit.

A port combination listed in a table shown in Table 4 may basicallycover all configurations of twelve or less ports, where reserved may beused for an additional combination to increase scheduling flexibility,although the listed combinations have satisfied a schedulingrequirement.

The DMRS configuration information table shown in Table 4 is applicableto an orthogonal DMRS implementing a maximum of twelve streams/layers ofdata transmission or a pattern corresponding to FIG. 10 (config. 2-2symbols).

The DMRS configuration information table in this embodiment is designedbased on an LTE table (in other words, columns are divided based on acodeword number), and a corresponding value requires five bits ofindication overheads.

According to the embodiment shown in Table 1 to Table 4, designing acorresponding DMRS configuration information table for each maximumsupported orthogonal-port quantity can satisfy requirements fordifferent scenarios in an NR system. For example, a table is not onlyapplied to a pattern in an ultra-reliable and low latency communication(URLLC) scenario but also applied to a pattern in Enhanced MobileBroadband (eMBB). For other different patterns, a design of the table isre-considered.

In this embodiment, a plurality of DMRS configuration information tablesare designed. The plurality of DMRS configuration information tables mayalso be different DMRS configuration information tables designed forDMRS pattern configuration types, which are briefly referred to as DMRSconfiguration types. Before transmission, based on differentconfiguration type information, a DMRS configuration information tableis selected or switching is performed between different informationtables.

There are two configuration types, and DMRS configuration informationtables corresponding to the two configuration types are respectivelyTable 3 in which a maximum of eight ports are shown (configurationtype 1) and Table 4 in which a maximum of 12 ports (configuration type2) are shown. The two tables are the same, and details are not describedherein again. The DMRS configuration information tables shown in Table 1to Table 4 correspond to different DMRS patterns, or correspond tomaximum supported orthogonal-port quantities that are supported by asystem, or correspond to different DMRS configuration types. Thepatterns, the maximum supported orthogonal-port quantities 4, 6, 8, and12, the DMRS configuration types, or the like that correspond to theDMRS configuration information tables may be indicated by using explicitsignaling such as RRC, a MAC CE, or DCI, or may be bound with anotherconfiguration parameter, for example, a frequency, a carrier spacing, ora frame structure, corresponding to a scenario.

Embodiment 2

This embodiment describes a column arrangement design manner of a DMRSconfiguration information table. Different from a column arrangementmanner in LTE, in this embodiment, division is not performed based on acodeword number. Instead, division is performed according to a ratio andbased on a maximum supported orthogonal-port quantity. Alternatively,information is grouped into two columns, where information correspondingto which a quantity of orthogonal ports is greater than a specific valuebelongs to one column, and information corresponding to which a quantityof orthogonal ports is less than or equal to the specific value belongsto the other column. Alternatively, column arrangement is performedbased on a quantity of transmission layers (in other words, UE RANK) ofthe receive end.

As shown in Table 5, that the maximum supported orthogonal-port quantityis equal to 12 is used as an example for description. The left column inthe information table is information corresponding to which a quantityof orthogonal ports is less than or equal to 8, and the right column isinformation corresponding to which a quantity of orthogonal ports isgreater than 8.

TABLE 5 Column arrangement is performed based on a ratio of a totalquantity of ports Total quantity of layers or config. 2-2-symbolpattern, ratio being 2/3 Total layer number ≤ 8 Total layer number > 8Value Total UE rank Ports Value Total UE rank Ports 0 4 1 0 0 12 1 0 1 41 1 1 12 1 1 2 4 1 2 2 12 1 2 3 4 1 3 3 12 1 3 4 4 2 0-1 4 12 1 4 5 4 22-3 5 12 1 5 6 4 3 0-2 6 12 1 6 7 4 4 0-3 7 12 1 7 8 8 1 0 8 12 1 8 9 81 1 9 12 1 9 10 8 1 2 10 12 1 10  11 8 1 3 11 12 1 11  12 8 1 4 12 12 20-1 13 8 1 5 13 12 2 2-3 14 8 1 6 14 12 2 4-5 15 8 1 7 15 12 2 6-7 16 82 0-1 16 12 2 8-9 17 8 2 2-3 17 12 2 10-11 18 8 2 4-5 18 12 3 0-2 19 8 26-7 19 12 3 3-5 20 8 3 0-2 20 12 3 6-8 21 8 3 3-5 21 12 3  9-11 22 8 40-3 22 12 4 0-3 23 8 4 4-7 23 12 4 4-7 24 8 5 0-4 24 12 4  8-11 25 8 60-5 25 26 8 7 0-6 26 27 8 8 0-7 27

Table 5 shows that column arrangement is performed on the informationtable by dividing a maximum supported orthogonal-port quantity by 2.This is only an example, and in this embodiment of this application,there may also be another column arrangement manner. As shown in Table 6and Table 7, division is performed based on a quantity of transmissionlayers (RANK) of UE. A principle is to enable quantities of rows ofeffective information on both columns to be balanced as far as possible,thereby reducing storage overheads.

TABLE 6 DMRS for a maximum of six ports One Codeword Two Codewords (≤4layers): (>4 layers): Codeword 0 enabled, Codeword 0 enabled, Codeword 1disabled Codeword 1 enabled Value UE rank Port index Value UE rank Portindex 0 1 0 0 5 0-4 1 1 1 1 6 0-5 2 1 2 2 2 0-1 3 1 3 3 2 2-3 4 1 4 4 24-5 5 1 5 5 3 0-2 6 6 3 3-5 7 7 4 0-3

TABLE 7 DMRS for a maximum of four ports One Codeword (≤4 layers): TwoCodewords (>4 layers): Codeword 0 enabled, Codeword 0 enabled, Codeword1 disabled Codeword 1 enabled Value UE rank Port index Value UE rankPort index 0 1 1 layer, port 0 0 2 2 layers, ports 0-1 1 1 1 layer, port1 1 2 2 layers, ports 2-3 2 1 1 layer, port 2 2 3 3 layers, ports 0-2 31 1 layer, port 3 3 4 4 layers, ports 0-3

Embodiment 3

In this embodiment, a plurality of DMRS configuration information tablesare integrated into a general information table, and selection isperformed based on a maximum supported orthogonal-transmission-layerquantity, a pattern, or higher layer signaling, specifically as shown inTable 8-0.

TABLE 8-0 DMRS for a maximum of 12 ports Value UE rank Port index 0 1 01 1 1 2 1 2 3 1 3 4 2 0-1 5 2 2-3 6 3 0-2 7 4 0-3 8 1 4 9 1 5 10 2 4-511 3 3-5 12 5 0-4 13 6 0-5 14 1 6 15 1 7 16 2 6-7 17 7 0-6 18 8 0-7 19 44-7 20 1 8 21 1 9 22 1 10  23 1 11  24 2 8-9 25 2 10-11 26 3 6-8 27 3 9-11 28 4  8-11 29 reserved reserved 30 reserved reserved 31 reservedreserved

A maximum quantity of orthogonal ports that is supported by the DMRSconfiguration information table shown in Table 8-0 is 12, DMRSconfiguration information corresponding to other port quantities such as4, 6, or 8 are all subsets of the general information table. When DMRSconfiguration information is selected, a corresponding sub-table may beselected from the general information table based on a maximum supportedorthogonal-port quantity, based on binding with a pattern, or based onan indication of higher layer signaling such as RRC signaling. Forexample, values 0 to 7 correspond to a total quantity 4 of orthogonalports, values 0 to 13 correspond to a total quantity 6 of orthogonalports, values 0 to 19 correspond to a total quantity 8 of orthogonalports, and values 0 to 28 correspond to a total quantity 12 oforthogonal ports.

According to the DMRS sending method provided in this application,designing a plurality of DMRS configuration information tables canreduce overheads for NR DMRS port indication.

In addition, in a specific implementation of integrating a plurality ofDMRS configuration information tables into a general information table,DMRS configuration information of a same DMRS configuration type may bedesigned in one general table, and is selected based on DMRS symbolinformation.

Specifically, the DMRS configuration information table may includesymbol information of a front-loaded (FL) DMRS, for example, a symbolquantity of the DMRS, where Table 8-1 corresponds to an FL DMRSconfiguration type 1, and Table 8-2 corresponds to an FL DMRSconfiguration type 2. In other words, each table corresponds to adifferent FL DMRS type. In addition, the table may further include stateinformation of a CDM group (State of CDM group), and the stateinformation of the CDM group may be used as rate matching information.

Columns in number of symbols in Table 8-1 and Table 8-2 respectivelycorrespond to a 1-symbol FL DMRS type 1 and a 2-symbol FL DMRS type 1.In this embodiment of this application, DMRS port indication informationof the 1-symbol FL DMRS type 1 and the 2-symbol FL DMRS type 1 of a sameFL DMRS configuration type are included in one table, and beneficialeffects thereof may be indicating different states in a table by usingDCI, to implement dynamic switching between the 1-symbol FL DMRS and the2-symbol FL DMRS.

In addition, the following gives only an example. States of the symbolquantity are 1 and 2, respectively corresponding to the 1-symbol FL DMRSand the 2-symbol FL DMRS. In an implementation, the symbol quantity maybe represented by 0 and 1. For example, 0 corresponds to the 1-symbol FLDMRS and 1 corresponds to the 2-symbol FL DMRS, or the 1-symbol isrepresented as a single symbol and the 2-symbol is represented as doublesymbols. During specific implementation, there may be a plurality ofrepresentation methods. This is not limited in this embodiment of thisapplication.

In another implementation, the column of the number of symbols may notbe added to the DMRS configuration information table, but is directlyimplicitly indicated by using a value. For example, the column of thenumber of symbols may be removed in Table 8-1 and Table 8-2, but otherelements remain unchanged. In this case, the transmit end can stillcomplete dynamic switching between the 1-symbol FL DMRS and the 2-symbolFL DMRS by indicating a value to the receive end.

For example, in Table 8-1, value=18 includes a DMRS port number whosevalue is greater than 3, and port numbers of a 1-symbol FL DMRS type 1are 0 to 3. In this way, the receive end can know that a 2-symbol DMRSpattern has been scheduled. In an implementation, the receive end andthe transmit end may predefine some values to correspond to a 1-symbolFL DMRS pattern. However, some values correspond to the 2-symbol FL DMRSpattern. For example, in Table 8-1, it may be predefined that values 0to 10 correspond to the 1-symbol FL DMRS, and values greater than 11correspond to the 2-symbol FL DMRS. In this case, for same schedulingcontent, value=0 corresponds to the 1-symbol FL DMRS, and value=11corresponds to the 2-symbol FL DMRS. The receive end learns, byindicating a value 0 and a value 11, that the 1-symbol FL DMRS patternor the 2-symbol FL DMRS pattern is currently scheduled.

TABLE 8-1 Example of a port combination of a configuration type 1 inwhich a symbol quantity is considered One Codeword (≤4 layers): TwoCodewords (>4 layers): Codeword 0 enabled, Codeword 0 enabled, Codeword1 disabled Codeword 1 enabled RMI or RMI or State of number State ofnumber CDM of CDM of Value group UE rank Ports symbols value group UErank Ports symbols 0 1 1 0 1 0 Reserved Reserved Reserved 1 1 1 1 1 1 1Reserved Reserved Reserved 1 2 1 2 0-1 1 2 Reserved Reserved Reserved 13 2 1 0 1 3 Reserved Reserved Reserved 1 4 2 1 1 1 4 Reserved ReservedReserved 1 5 2 1 2 1 5 Reserved Reserved Reserved 1 6 2 1 3 1 6 ReservedReserved Reserved 1 7 2 2 0-1 1 7 Reserved Reserved Reserved 1 8 2 2 2-31 8 Reserved Reserved Reserved 1 9 2 3 0-2 1 9 Reserved ReservedReserved 1 10 2 4 0-3 1 10 Reserved Reserved Reserved 1 11 1 1 0 2 11 25 0-4 2 12 1 1 1 2 12 2 6 0-5 2 13 1 1 4 2 13 2 7 0-6 2 14 1 1 6 2 14 28 0-7 2 15 1 2 0-1 2 15 Reserved Reserved Reserved 2 16 1 2  4, 6 2 16Reserved Reserved Reserved 2 17 1 3 0-1, 4 2 17 Reserved ReservedReserved 2 18 1 4 0-1, 4, 6 2 18 Reserved Reserved Reserved 2 19 2 1 0 219 Reserved Reserved Reserved 2 20 2 1 1 2 20 Reserved Reserved Reserved2 21 2 1 2 2 21 Reserved Reserved Reserved 2 22 2 1 3 2 22 ReservedReserved Reserved 2 23 2 1 4 2 23 Reserved Reserved Reserved 2 24 2 1 52 24 Reserved Reserved Reserved 2 25 2 1 6 2 25 Reserved ReservedReserved 2 26 2 1 7 2 26 Reserved Reserved Reserved 2 27 2 2 0-1 2 27Reserved Reserved Reserved 2 28 2 2 2-3 2 28 Reserved Reserved Reserved2 29 2 2  4, 6 2 29 Reserved Reserved Reserved 2 30 2 2  5, 7 2 30Reserve Reserved Reserved 2 31 2 3 0-1, 4 2 31 Reserved ReservedReserved 2 32 2 3 2-3, 5 2 32 Reserved Reserved Reserved 2 33 2 4 0-1,4, 6 2 33 Reserved Reserved Reserved 2 34 2 4 2-3, 5, 7 2 34 ReservedReserved Reserved 2

TABLE 8-2 Example of a port combination of a configuration type 2 inwhich a symbol quantity is considered One Codeword (≤4 layers): TwoCodewords (>4 layers): Codeword 0 enabled, Codeword 0 enabled, Codeword1 disabled Codeword 1 enabled State of number State of number CDM of CDMof Value group UE rank Ports symbols Value group UE rank Ports symbols 01 1 0 1 0 3 5 0-4 1 1 1 1 1 1 1 3 6 0-5 1 2 1 2 0-1 1 2 ReservedReserved Reserved 1 3 2 1 0 1 3 Reserved Reserved Reserved 1 4 2 1 1 1 4Reserved Reserved Reserved 1 5 2 1 2 1 5 Reserved Reserved Reserved 1 62 1 3 1 6 Reserved Reserved Reserved 1 7 2 2 0-1 1 7 Reserved ReservedReserved 1 8 2 2 2-3 1 8 Reserved Reserved Reserved 1 9 2 3 0-2 1 9Reserved Reserved Reserved 1 10 2 4 0-3 1 10 Reserved Reserved Reserved1 11 3 1 0 1 11 Reserved Reserved Reserved 1 12 3 1 1 1 12 ReservedReserved Reserved 1 13 3 1 2 1 13 Reserved Reserved Reserved 1 14 3 1 31 14 Reserved Reserved Reserved 1 15 3 1 4 1 15 Reserved ReservedReserved 1 16 3 1 5 1 16 Reserved Reserved Reserved 1 17 3 2 0-1 1 17Reserved Reserved Reserved 1 18 3 2 2-3 1 18 Reserved Reserved Reserved1 19 3 2 4-5 1 19 Reserved Reserved Reserved 1 20 3 3 0-2 1 20 ReservedReserved Reserved 1 21 3 3 3-5 1 21 Reserved Reserved Reserved 1 22 3 40-3 1 22 Reserved Reserved Reserved 1 23 1 1 0 2 23 2 5 0-2, 6, 9 2 24 11 1 2 24 2 6 0-3, 6, 9 2 25 1 1 6 2 25 2 7 0-3, 6, 7, 9 2 26 1 1 9 2 262 8 0-3, 6, 7, 9, 10 2 27 1 2 0-1 2 27 Reserved Reserved Reserved 2 28 12  6, 9 2 28 Reserved Reserved Reserved 2 29 1 3 0-1, 6 2 29 ReservedReserved Reserved 2 30 1 4 0-1, 6, 9 2 30 Reserved Reserved Reserved 231 2 1 0 2 31 Reserved Reserved Reserved 2 32 2 1 1 2 32 ReservedReserved Reserved 2 33 2 1 2 2 33 Reserved Reserved Reserved 2 34 2 1 32 34 Reserved Reserved Reserved 2 35 2 1 6 2 35 Reserved ReservedReserved 2 36 2 1 7 2 36 Reserved Reserved Reserved 2 37 2 1 9 2 37Reserved Reserved Reserved 2 38 2 1 10  2 38 Reserved Reserved Reserved2 39 2 2 0-1 2 39 Reserved Reserved Reserved 2 40 2 2  6, 9 2 40Reserved Reserved Reserved 2 41 2 2 2-3 2 41 Reserved Reserved Reserved2 42 2 2    7, 10 2 42 Reserved Reserved Reserved 2 43 2 3 0-1, 6 2 43Reserved Reserved Reserved 2 44 2 3 2-3, 7 2 44 Reserved ReservedReserved 2 45 2 4 0-1, 6, 9 2 45 Reserved Reserved Reserved 2 46 2 42-3, 7, 10 2 46 Reserved Reserved Reserved 2 47 3 1 0 2 47 ReservedReserved Reserved 2 48 3 1 1 2 48 Reserved Reserved Reserved 2 49 3 1 22 49 Reserved Reserved Reserved 2 50 3 1 3 2 50 Reserved ReservedReserved 2 51 3 1 4 2 51 Reserved Reserved Reserved 2 52 3 1 5 2 52Reserved Reserved Reserved 2 53 3 1 6 2 53 Reserved Reserved Reserved 254 3 1 7 2 54 Reserved Reserved Reserved 2 55 3 1 8 2 55 ReservedReserved Reserved 2 56 3 1 9 2 56 Reserved Reserved Reserved 2 57 3 110  2 57 Reserved Reserved Reserved 2 58 3 1 11  2 58 Reserved ReservedReserved 2 59 3 2 0-1 2 59 Reserved Reserved Reserved 2 60 3 2  6, 9 260 Reserved Reserved Reserved 2 61 3 2 2-3 2 61 Reserved ReservedReserved 2 62 3 2    7, 10 2 62 Reserved Reserved Reserved 2 63 3 2 4-52 63 Reserved Reserved Reserved 2 64 3 2    8, 11 2 64 Reserved ReservedReserved 2 65 3 3 0-1, 6 2 65 Reserved Reserved Reserved 2 66 3 3 2-3, 72 66 Reserved Reserved Reserved 2 67 3 3 4-5, 8 2 67 Reserved ReservedReserved 2 68 3 3  9-11 2 68 Reserved Reserved Reserved 2 69 3 4 0-1, 6,9 2 69 Reserved Reserved Reserved 2 70 3 4 2-3, 7, 10 2 70 ReservedReserved Reserved 2 71 3 4 4-5, 8, 11 2 71 Reserved Reserved Reserved 2

In an implementation method, the transmit end, for example, a networkside device, may schedule only a part of a table during specificscheduling, to be specific, a sub-table or a subset of a table, therebyreducing DCI overheads.

In an implementation, selection of the sub-table may be explicitlyconfigured by using RRC signaling. In other words, the DMRS symbolinformation is indicated by using RRC signaling, to dynamically schedulethe DMRS configuration type corresponding to the 1-symbol or the DMRSconfiguration type corresponding to the 2-symbol.

For example, in Table 8-2, RRC signaling may instruct to activate atable corresponding to the 1-symbol FL DMRS, for example values 0 to 22(in other words, a number of symbols=1) in Table 8-2, or indicate thatthe entire table can be used, for example, all rows (in other words, anumber of symbols=1 and a number of symbols=2) in Table 8-2. Duringspecific implementation, the configuration based on the RRC signalingmay be implemented in a plurality of manners. For example, independentRRC signaling may be used for configuration, or the RRC signaling may bebound with other RRC signaling indicating FL DMRS indication informationto perform implicit indication.

During explicit indication, independent RRC signaling may be used forconfiguration. For example, in RRC signaling, set1 and set2 areconfigured to correspond to some predefined state sets (for example,set1 corresponds to a state in a case of a number of symbols=1, and set2corresponds to all states in the table), or it is directly indicatedthat first some states (value) are activated (for example, in Table 8-1,‘1010/binary’ indicates that first 11 values 0 to 10 are used, or avalue is directly indicated, where all values before the value areactivated), or an on/off state is configured for enabling (for example,off represents that the only a number of symbols=1 is used, and onrepresents an entire table is used), or a bitmap is used toindependently indicate each value in a table. A specific RRCconfiguration method is not limited herein.

In another implementation, enabling of a sub-table may be bound withother RRC signaling, for example, may be bound with a parameter that isin RRC and that indicates a maximum number of symbols of an FL DMRS, andfor example, bound with DL-DMRS-max-len or UL-DMRS-max-len. Thefollowing uses DL as an example. When DL-DMRS-max-len=1, it indicatesthat a maximum number of symbols of an FL DMRS is 1. In other words, thesystem invokes only a 1-symbol FL DMRS. In this case, the receive endand the transmit end use only a state corresponding to the 1-symbol FLDMRS in Table 8-2, for example, a value is any one of 0 to 22. WhenDL-DMRS-max-len=2, it indicates that a maximum number of symbols of anFL DMRS is 2. In other words, the system can invoke a 1-symbol FL DMRSpattern and a 2-symbol FL DMRS. In this case, the receive end and thetransmit end can use states corresponding to the 1-symbol FL DMRS andthe 2-symbol FL DMRS in Table 8-2. In other words, states in the entiretable can be used.

In addition, in cases of different maximum symbol quantities of an FLDMRS (for example, when DL-DMRS-max-len or UL-DMRS-max-len in the RRCsignaling is equal to 1 or 2), lengths of DCI signaling forcorresponding DMRS port scheduling are different, quantities of bits aredifferent, or DCI fields are different.

Embodiment 4

In this embodiment, the method provided in this application is appliedto specific implementations of various NR scenarios. Specifically, in a2-PDCCH or 1-PDCCH non-coherent joint transmission (NC-JT) scenario, aplurality of DMRS configuration information tables bound with a patternare set for two transmission reception points (TRPs).

In this embodiment, ports are selected from different DMRS port groupsto form port combinations. In a single-PDCCH scenario, a base stationneeds to notify scheduling UE of the port combinations by using onepiece of DCI, while in a dual-PDCCH scenario, may notify UE of the portcombinations by using two pieces of DCI. Division of a DMRS port groupis related to a pattern configuration and a port mapping scheme. Forexample, there may be two port mapping schemes for a configuration type1, as shown in FIG. 11 or FIG. 12, and there may be three port mappingschemes for a configuration type 2, respectively as shown in FIG. 13,FIG. 14, and FIG. 15.

The foregoing various port mapping schemes are obtained by sequentiallyperforming code division multiplexing and frequency divisionmultiplexing on ports, or by sequentially performing frequency divisionmultiplexing and code division multiplexing on ports. Different DMRSport groups may be obtained through various different port mapping, anda grouping basis is that ports on which code division multiplexing isperformed can be located only in a same group.

For example, DMRS groups in FIG. 11 are {(0, 2, 4, 6), (1, 3, 5, 7)} orsubsets of each group, for example, {(0, 2), (1, 3)};

DMRS groups in FIG. 12 are {(0, 1, 4, 6), (2, 3, 5, 7)} or subsets ofeach group;

DMRS groups in FIG. 13 are {(0, 1, 6, 7), (2, 3, 4, 5, 8, 9, 10, 11)},{(0, 1, 6, 7, 4, 5, 10, 11), (2, 3, 8, 9)}, {(0, 1, 6, 7, 2, 3, 8, 9),(4, 5, 10, 11)}, or subsets of each group;

DMRS groups in FIG. 14 are {(0, 3, 6, 9), (1, 4, 7, 10, 2, 5, 8, 11)},{(0, 3, 6, 9, 1, 4, 7, 10), (2, 5, 8, 11)}, {(1, 4, 7, 10), (0, 3, 6, 9,2, 5, 8, 11)}, or subsets of each group; and

DMRS groups in FIG. 15 are {(0, 1, 6, 9), (2, 3, 7, 10, 4, 5, 8, 11)},{(0, 1, 6, 9, 4, 5, 8, 11), (2, 3, 7, 10)}, {(4, 5, 8, 11), (0, 1, 6, 9,2, 3, 7, 10)}, or subsets of each group.

In this embodiment, ports need to be selected from different groups, toform port combinations. Therefore, different port groups form differentport combinations. In the following, a DMRS configuration informationtable is designed by using one port mapping scheme in each configurationas an example.

For example, FIG. 16 is a schematic diagram of mapping between a patternand a port in NC-JT. A corresponding quasi co-location (QCL) groupstatus is that a TRP 1 uses a port group including ports {0, 1, 6, 9},and a TRP 2 uses ports {2, 3, 4, 5, 7, 8, 10, 11}.

To support an NC-JT 1-PDCCH scenario shown in FIG. 16, a DMRSconfiguration information table shown in Table 9 is based on the DMRSconfiguration information table shown in Table 4, where rowscorresponding to values 25 to 32 are added to the left column, and rowscorresponding to values 4 to 18 are added to the right column. Forspecific content, refer to Table 9.

TABLE 9 DMRS for a maximum of 12 ports (pattern config. 2-2 symbols),single PDCCH One Codeword (≤4 layers): Two Codewords (>4 layers):Codeword 0 enabled, Codeword 0 enabled, Codeword 1 disabled Codeword 1enabled Value UE rank Port index Value UE rank Port index 0 1 0 0 5 0-4(SU) 1 1 1 1 6 0-5 (SU) 2 1 2 2 7 0-6 (SU) 3 1 3 3 8 0-7 (SU) 4 1 4 4 51, 2-5 5 1 5 5 5 7-11 6 1 6 6 5 5-9 7 1 7 7 5 0-3, 6 8 1 8 8 5 0-2, 6, 99 1 9 9 6 3-8 10 1 10  10 6 6-11 11 1 11  11 6 0-4, 6 12 2 0-1 12 6 0-3,6, 9 13 2 2-3 13 7 2-8 14 2 4-5 14 7 1-7 15 2 6-7 15 7 0-4, 6, 9 16 28-9 16 8 2-8, 10 17 2 10-11 17 8 0-5, 7-8 18 3 0-2 18 8 0-6, 9 19 3 3-519 Reserved Reserved 20 3 6-8 20 Reserved Reserved 21 3  9-11 21Reserved Reserved 22 4 0-3 22 Reserved Reserved 23 4 4-7 23 ReservedReserved 24 4  8-11 24 Reserved Reserved 25 2 0, 2 25 Reserved Reserved26 2 1, 3 26 Reserved Reserved 27 3 6-7, 9 27 Reserved Reserved 28 3 8,10-11 28 Reserved Reserved 29 3 0, 2-3 29 Reserved Reserved 30 3 1, 4-530 Reserved Reserved 31 4 6-9 31 Reserved Reserved 32 4 0-1, 2, 6 32Reserved Reserved

To support an NC-JT 2-PDCCH scenario shown in FIG. 16, a DMRSconfiguration information table shown in Table 10 is based on the DMRSconfiguration information table shown in Table 4, where rowscorresponding to values 25 to 32 are added to the left column, and rowscorresponding to values 4 to 7 are added to the right column. Forspecific content, refer to Table 10.

TABLE 10 DMRS for a maximum of 12 ports (pattern config. 2-2 symbols),two PDCCHs One Codeword (≤4 layers): Two Codewords (>4 layers): Codeword0 enabled, Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabledValue UE rank Port index Value UE rank Port index 0 1 0 0 5 0-4 (SU) 1 11 1 6 0-5 (SU) 2 1 2 2 7 0-6 (SU) 3 1 3 3 8 0-7 (SU) 4 1 4 4 6 2-7 5 1 55 6 2-5, 7-8 6 1 6 6 5 2-5, 7 7 1 7 7 7 2-5, 7-8, 10 8 1 8 8 ReservedReserved 9 1 9 9 Reserved Reserved 10 1 10 10 Reserved Reserved 11 1 1111 Reserved Reserved 12 2 0-1 12 Reserved Reserved 13 2 2-3 13 ReservedReserved 14 2 4-5 14 Reserved Reserved 15 2 6-7 15 Reserved Reserved 162 8-9 16 Reserved Reserved 17 2 10-11 17 Reserved Reserved 18 3 0-2 18Reserved Reserved 19 3 3-5 19 Reserved Reserved 20 3 6-8 20 ReservedReserved 21 3  9-11 21 Reserved Reserved 22 4 0-3 22 Reserved Reserved23 4 4-7 23 Reserved Reserved 24 4  8-11 24 Reserved Reserved 25 2 7-825 Reserved Reserved 26 2 6, 9 26 Reserved Reserved 27 3 7-8, 10 27Reserved Reserved 28 3 0-1, 6 28 Reserved Reserved 29 4 2-5 29 ReservedReserved 30 4 7-8, 10-11 30 Reserved Reserved 31 4 0, 1, 6, 9 31Reserved Reserved

FIG. 17 is another schematic diagram of mapping between a pattern and aport corresponding to NC-JT. A corresponding quasi co-location (QCL)group status is that a TRP 1 uses a port group including ports {0, 2, 4,6}, and a TRP 2 uses ports {1, 3, 5, 7}.

To support an NC-JT 1-PDCCH scenario shown in FIG. 17, a DMRSconfiguration information table shown in Table 11 is based on the DMRSconfiguration information table shown in Table 3, where rowscorresponding to values 16 to 19 are added to the left column, and rowscorresponding to values 4 to 10 are added to the right column. Forspecific content, refer to Table 11.

TABLE 11 DMRS for a maximum of eight ports (pattern config. 1-2symbols), single PDCCH One Codeword Two Codewords (≤4 layers): (>4layers): Codeword 0 enabled, Codeword 0 enabled, Codeword 1 disabledCodeword 1 enabled Value UE rank Port index Value UE rank Port index 0 10 0 5 0-4 1 1 1 1 6 0-5 2 1 2 2 7 0-6 3 1 3 3 8 0-7 4 1 4 4 5 0-2, 4, 65 1 5 5 5 0-2, 3-4 6 1 6 6 5 1-5 7 1 7 7 5 1-3, 5, 7 8 2 0-1 8 6 0-3, 4,6 9 2 2-3 9 6 0-3, 5, 7 10 2 4-5 10 7 1-7 11 2 6-7 11 12 3 0-2 12 13 33-5 13 14 4 0-3 14 15 4 4-7 15 16 3 4-6 16 17 3 1, 6-7 17 18 4 0-2, 4 1819 4 1-3, 5 19

To support an NC-JT 2-PDCCH scenario shown in FIG. 17, a DMRSconfiguration information table shown in Table 12 is based on the DMRSconfiguration information table shown in Table 3, where rowscorresponding to values 16 to 23 are added to the left column. Forspecific content, refer to Table 12.

TABLE 12 DMRS for a maximum of eight ports (pattern config. 1-2symbols), two PDCCHs One Codeword (≤4 layers): Two Codewords (>4layers): Codeword 0 enabled, Codeword 0 enabled, Codeword 1 disabledCodeword 1 enabled Value UE rank Port index Value UE rank Port index 0 10 0 5 0-4 1 1 1 1 6 0-5 2 1 2 2 7 0-6 3 1 3 3 8 0-7 4 1 4 4 ReservedReserved 5 1 5 5 Reserved Reserved 6 1 6 6 Reserved Reserved 7 1 7 7Reserved Reserved 8 2 0-1 8 Reserved Reserved 9 2 2-3 9 ReservedReserved 10 2 4-5 10 Reserved Reserved 11 2 6-7 11 Reserved Reserved 123 0-2 12 Reserved Reserved 13 3 3-5 13 Reserved Reserved 14 4 0-3 14Reserved Reserved 15 4 4-7 15 Reserved Reserved 16 2 1, 3 16 ReservedReserved 17 2 5, 7 17 Reserved Reserved 18 2 0, 2 18 Reserved Reserved19 2 4, 6 19 Reserved Reserved 20 3 1, 3, 5 20 Reserved Reserved 21 3 0,2, 4 21 Reserved Reserved 22 4 1, 3, 5, 7 22 Reserved Reserved 23 4 0,2, 4, 6 23 Reserved Reserved

FIG. 18 is another schematic diagram of mapping between a pattern and aport corresponding to NC-JT. A corresponding quasi co-location (QCL)group status is that a TRP 1 uses a port group including ports 10, 11,and a TRP 2 uses ports {2, 3, 4, 5}.

To support an NC-JT 1-PDCCH scenario shown in FIG. 18, a DMRSconfiguration information table shown in Table 13 is based on the DMRSconfiguration information table shown in Table 2, where rowscorresponding to values 12 to 15 are added to the right column, and arow corresponding to a value 2 is added to the left column. For specificcontent, refer to Table 13.

TABLE 13 DMRS for a maximum of six ports (pattern config 2-1 symbol),single PDCCH One Codeword (≤4 layers): Two Codewords (>4 layers):Codeword 0 enabled, Codeword 0 enabled, Codeword 1 disabled Codeword 1enabled Value UE rank Port index Value UE rank Port index 0 1 0 0 5 0-4(SU) 1 1 1 1 6 0-5 (SU) 2 1 2 2 5 0, 2-5 3 1 3 3 Reserved Reserved 4 1 44 Reserved Reserved 5 1 5 5 Reserved Reserved 6 2 0-1 6 ReservedReserved 7 2 2-3 7 Reserved Reserved 8 2 4-5 8 Reserved Reserved 9 3 0-29 Reserved Reserved 10 3 3-5 10 Reserved Reserved 11 4 0-3 11 ReservedReserved 12 2 0, 2 12 Reserved Reserved 13 2 1, 3 13 Reserved Reserved14 3 0, 2, 3 14 Reserved Reserved 15 4 0, 2-4 15 Reserved Reserved 16Reserved Reserved 16 Reserved Reserved

To support an NC-JT 2-PDCCH scenario shown in FIG. 28, a DMRSconfiguration information table shown in Table 14 is based on the DMRSconfiguration information table shown in Table 2, where a rowcorresponding to a value 12 is added to the left column. For specificcontent, refer to Table 14.

TABLE 14 DMRS for a maximum of six ports (pattern config 2-1 symbol),two PDCCHs One Codeword (≤4 layers): Two Codewords (>4 layers): Codeword0 enabled, Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabledValue UE rank Port index Value UE rank Port index 0 1 0 0 5 0-4 (SU) 1 11 1 6 0-5 (SU) 2 1 2 2 Reserved Reserved 3 1 3 3 Reserved Reserved 4 1 44 Reserved Reserved 5 1 5 5 Reserved Reserved 6 2 0-1 6 ReservedReserved 7 2 2-3 7 Reserved Reserved 8 2 4-5 8 Reserved Reserved 9 3 0-29 Reserved Reserved 10 3 3-5 10 Reserved Reserved 11 4 0-3 11 ReservedReserved 12 4 2-5 12 Reserved Reserved 13 Reserved Reserved 13 ReservedReserved 14 Reserved Reserved 14 Reserved Reserved 15 Reserved Reserved15 Reserved Reserved 16 Reserved Reserved 16 Reserved Reserved

FIG. 19 is another schematic diagram of mapping between a pattern and aport corresponding to NC-JT. A corresponding quasi co-location (QCL)group status is that a TRP 1 uses a port group including ports {0, 2},and a TRP 2 uses ports {1, 3}.

To support an NC-JT 1-PDCCH scenario shown in FIG. 19, a DMRSconfiguration information table shown in Table 15-1 is based on the DMRSconfiguration information table shown in Table 1, where a rowcorresponding to a value 8 is added to the right column. For specificcontent, refer to Table 15-1.

TABLE 15-1 DMRS for a maximum of four ports (pattern config. 1-1symbol), single PDCCH One Codeword (≤4 layers): Two Codewords (>4layers): Codeword 0 enabled, Codeword 0 enabled, Codeword 1 disabledCodeword 1 enabled Value UE rank Port index Value UE rank Port index 0 10 0 Reserved Reserved 1 1 1 1 Reserved Reserved 2 1 2 2 ReservedReserved 3 1 3 3 Reserved Reserved 4 2 0-1 4 Reserved Reserved 5 2 2-3 5Reserved Reserved 6 3 0-2 6 Reserved Reserved 7 4 0-3 7 ReservedReserved 8 3 1-3 8 Reserved Reserved

To support an NC-JT 2-PDCCH scenario shown in FIG. 19, a DMRSconfiguration information table shown in Table 15-2 is based on the DMRSconfiguration information table shown in Table 1, where rowscorresponding to values 8 and 9 are added to the left column. Forspecific content, refer to Table 15-2.

TABLE 15-2 DMRS for a maximum of four ports (pattern config 1-1 symbol),two PDCCHs One Codeword (≤4 layers): Two Codewords (>4 layers): Codeword0 enabled, Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabledValue UE rank Port index Value UE rank Port index 0 1 0 0 ReservedReserved 1 1 1 1 Reserved Reserved 2 1 2 2 Reserved Reserved 3 1 3 3Reserved Reserved 4 2 0-1 4 Reserved Reserved 5 2 2-3 5 ReservedReserved 6 3 0-2 6 Reserved Reserved 7 4 0-3 7 Reserved Reserved 8 2 1,3 8 Reserved Reserved 9 2 0, 2 9 Reserved Reserved

According to any one of Embodiment 1 to Embodiment 4, in different NRscenarios or for different transmission requirements, the transmit endselects suitable DMRS configuration information, obtains DMRS indicationinformation based on the selected DMRS configuration information, andthen sends the DMRS indication information to the receive end.

When receiving a value indicating the DMRS indication information, thereceive end demodulates a reference signal on a correspondingtime-frequency resource location based on a quantity of orthogonaltransmission layers or an orthogonal port number that is indicated bythe value, or based on a resource that is not occupied by a DMRS.

To facilitate scheduling by the base station, in an MU-MIMO scenario,for a particular receive end, the DMRS port is first scheduled from oneCDM group, and then scheduled across CDM groups. Such a scheduling rulemay be referred to as a CDM-first scheduling rule. Considering that aDMRS port indicates that a table includes both an SU state and an MUstate, particularly, for scheduling in SU-MIMO, different schedulingrules have different benefits. The following provides examples forspecific descriptions. The following port mapping orders are considered:

for a 1-symbol DMRS type 1, ports included in a CDM group 1 are {0, 1},and ports included in a CDM group 2 are {2, 3};

for a 2-symbol DMRS type 1, ports included in a CDM group 1 are {0, 1,4, 5}, and ports included in a CDM group 2 are {2, 3, 6, 7};

for a 1-symbol DMRS type 2, ports included in a CDM group 1 are {0, 1},ports included in a CDM group 2 are {2, 3}, and ports included in a CDMgroup 3 are {4, 5}; and

for a 2-symbol DMRS type 2, ports included in a CDM group 1 are {0, 1,6, 7}, ports included in a CDM group 2 are {2, 3, 8, 9}, and portsincluded in a CDM group 3 are {4, 5, 10, 11}.

For SU, the transmit end may allocate DMRS ports of the receive endaccording to the following rules. The following provides specificdescriptions. It should be noted that, a specific scheduling rule isonly provided herein. When the DMRS mapping rule changes, allocation ofa DMRS port number in an example may change, but the scheduling ruledoes not change.

CDM-first scheduling: For the receive end, a DMRS port is preferentiallyscheduled from one CDM group. When all port numbers in the CDM group areoccupied, scheduling is performed in another port group. The scheme hasan advantage that SU scheduling and MU scheduling have a same rule. Thefollowing provides a specific example for a DMRS type. The followingexample may be represented as a row (value) in a DMRS port schedulingtable (for example, Table 8-1 or Table 8-2).

For the 1-symbol DMRS type 1, when two layers of data of the receive endare scheduled, scheduled ports may be 0 and 1 (or 2 and 3). In otherwords, the scheduled ports are in a same CDM group. When three layers ofdata of the receive end are scheduled, scheduled ports may be 0, 1, and2. In other words, all ports in the CDM group 1 are scheduled, and then,the port 2 in the CDM group 2 is scheduled. Specifically, in Table 16-1,the following rows of downlink state information may be reflected.

TABLE 16-1 Example of a DMRS type 1 Number of co-scheduled number ofValue CDM groups UE rank Ports symbols X 1 2 0, 1 1 Y 2 3 0, 1, 2 1

For the 2-symbol DMRS type 1, when four layers of data of the receiveend are scheduled, scheduled ports may be 0, 1, 4, and 5. In otherwords, the scheduled ports are in a same CDM group. When five layers ofdata of the receive end are scheduled, scheduled ports may be 0, 1, 4,5, and 2. In other words, all ports in the CDM group 1 are scheduled,and then, a port in the CDM group 2 is scheduled. Specifically, in Table16-2, the following rows of downlink state information may be reflected.

TABLE 16-2 Example of a DMRS type 1 Number of co-scheduled UE number ofValue CDM groups rank Ports symbols X 1 4 0, 1, 4, 5 2 Y 2 5 0, 1, 2, 4,5 2

For the 1-symbol DMRS type 2, when three layers of data of the receiveend are scheduled, scheduled ports may be 0, 1, and 2. In other words,all ports in the CDM group 1 are scheduled, and then, a port in the CDMgroup 2 is scheduled. When five layers of data of the receive end arescheduled, scheduled ports may be 0, 1, 2, 3, and 4. In other words, allports in the CDM groups 1 and 2 are scheduled, and then, a port in theCDM group 3 is scheduled, as shown in Table 16-3:

TABLE 16-3 Example of a DMRS type 2 Number of co-scheduled UE number ofValue CDM groups rank Ports symbols X 2 3 0, 1, 2 1 Y 3 5 0, 1, 2, 3, 41

For the 2-symbol DMRS type 2, when three layers of data of the receiveend are scheduled, scheduled ports may be 0, 1, and 6. In other words,the CDM group 1 is occupied, or in other words, scheduling ispreferentially performed in the CDM group 1. When five layers of data ofthe receive end are scheduled, scheduled ports may be 0, 1, 6, 7, and 2.In other words, all ports in the CDM group 1 are scheduled, and then, aport in the CDM group 2 is scheduled, as shown in Table 16-4:

TABLE 16-4 Example of a DMRS type 2 Number of co-scheduled UE number ofValue CDM groups rank Ports symbols X 1 3 0, 1, 6 2 Y 2 5 0, 1, 2, 6, 72

FDM-first scheduling: For the receive end, DMRS port is first scheduledacross CDM groups. After a port in each CDM group is scheduled,scheduling continues to be performed across the CDM groups starting fromthe first CDM group. A main idea is to average quantities of DMRS portsscheduled in all CDM groups as far as possible. For example, when threeports are scheduled, for the type 2, one port is scheduled in each ofthe three CDM groups. This scheme has a characteristic of averaging aquantity of DMRS ports used in each CDM group during SU scheduling, sothat power in each CDM group is more averaged. A sequence of portnumbers provided below is only an example for better understanding.During specific implementation, a sequence of writing the port numbersis not limited. For example, 0, 2, 1, 3, and 4 may be written into 0, 1,2, 3, and 4.

For the 1-symbol DMRS type 1, when two layers of data of the receive endare scheduled, scheduled ports may be 0 and 2. In other words, ports arepreferentially scheduled across CDM groups. When three layers of data ofthe receive end are scheduled, scheduled ports may be 0, 1, and 2. Inother words, one port in each of the CDM groups 1 and 2 is scheduled,and then, a port in the CDM group 1 is scheduled, as shown in Table16-5:

TABLE 16-5 Example of a DMRS type 1 Number of co-scheduled number ofValue CDM groups UE rank Ports symbols X 2 2 0, 2 1 Y 2 3 0, 1, 2 1

For the 2-symbol DMRS type 1, when two layers of data of the receive endare scheduled, scheduled ports may be 0 and 2. In other words,scheduling is preferentially performed across CDM groups. When fivelayers of data of the receive end are scheduled, scheduled ports may be0, 2, 1, 3, 4. In other words, the scheduled DMRS ports are allocated inthe CDM groups as evenly as possible, as shown in Table 16-6:

TABLE 16-6 Example of a DMRS type 1 Number of co-scheduled UE number ofValue CDM groups rank Ports symbols X 2 2 0, 2 2 Y 2 5 0, 1, 2, 3, 4 2

For the 1-symbol DMRS type 2, when three layers of data of the receiveend are scheduled, scheduled ports may be 0, 2, and 4. In other words,one DMRS port in each of the CDM groups 1, 2, and 3 is occupied. Whenfour layers of data of the receive end are scheduled, scheduled portsmay be 0, 2, 4, and 1. In other words, a port in each of the CDM groups1, 2, and 3 is scheduled, and then, a port in the CDM group 1 isscheduled again, as shown in Table 16-7:

TABLE 16-7 Example of a DMRS type 2 Number of co-scheduled UE number ofValue CDM groups rank Ports symbols X 3 3 0, 2, 4 1 Y 3 4 0, 1, 2, 4 1

For the 2-symbol DMRS type 2, when three layers of data of the receiveend are scheduled, scheduled ports may be 0, 2, and 4. When eight layersof data of the receive end are scheduled, scheduled ports may be 0, 1,2, 3, 4, 5, 6, and 8, as shown in Table 16-8:

TABLE 16-8 Example of a DMRS type 1 Number of co-scheduled UE number ofValue CDM groups rank Ports symbols X 3 3 0, 2, 4 2 Y 3 8 0, 1, 2, 3, 4,5, 2 6, 8

In addition, for the FDM-first scheduling scheme, during specificimplementation, a number of CDM groups in FDM-first scheduling islimited to improve spectral efficiency of SU scheduling. For example, inthree CDM groups for the DMRS type 2, when SU is limited, FDM-firstscheduling may be performed on two of the CDM groups. In this case, forthe type 2, when six layers (or four DMRS ports) are scheduled,scheduled ports may be 0, 1, 2, 3, 6, and 8. In other words, both theCDM groups 1 and 2 are scheduled. When eight layers are scheduled,scheduled ports may be 0, 1, 2, 3, 6, 7, 8, and 9. In other words, threeports are scheduled in each of the CDM groups 1 and 2. This scheme hasan advantage that the CDM group 3 may be used to transmit data, therebyimproving spectral efficiency, as shown in Table 16-9:

TABLE 16-9 Example of a DMRS type 2 Number of co-scheduled UE number ofValue CDM groups rank Ports symbols X 2 6 0, 1, 2, 3, 6, 8 2 Y 2 8 0, 1,2, 3, 6, 7, 2 8, 9

Continuous port-number scheduling: For the receive end, DMRS ports arecontinuously scheduled in descending order of DMRS port numbers. Thisscheme has a characteristic of a simply designed table. For example,three layers correspond to DMRS port numbers 0 to 2, five layerscorrespond to DMRS port numbers 0 to 4, and eight layers correspond toDMRS port numbers 0 to 7.

During specific implementation, the foregoing scheduling rules may becombined or supplemented, or may exist at the same time. For example,for a table including both the 1-symbol and the 2-symbol DMRS type 1 (ortype 2), the table may include statuses of CDM-first scheduling,FDM-first scheduling, continuous port-number scheduling, to increaseflexibility of system scheduling.

In an implementation method, for a same number of symbols and a samequantity of scheduled layers, the table may include both statuses ofCDM-first scheduling and FDM-first scheduling, to improve schedulingflexibility or spectral efficiency, as shown in Table 16-10:

TABLE 16-10 Example of a DMRS type 1 Number of Value co-scheduled CDMgroups UE rank Ports number of symbols X 1 2 0, 1 1 Y 2 2 0, 2 1

Alternatively, in an implementation, in the table, the continuousport-number scheduling rule may be used for a case in which a quantityof layers is greater than a particular quantity of scheduled layers, andthe FDM or CDM-first scheduling rule may be used for a case in which aquantity of layers is less than the particular quantity of scheduledlayers, as shown in Table 16-11:

TABLE 16-11 Example of a DMRS type 1 Number of UE Value co-scheduled CDMgroups rank Ports number of symbols X 3 3 0, 2, 4 2 Y 2 8 0-7 2

Alternatively, in the table, different scheduling rules or a combinationof a plurality of rules may be used for a 1-symbol or 2-symbol FL DMRSconfiguration. For example, the FDM-first scheduling rule is used forthe 1-symbol DMRS type 2, and the FDM-first scheduling rule is used fortwo CDM groups for the 2-symbol type 2, thereby improving spectralefficiency of SU scheduling in the case of the 2-symbol type 2, as shownin Table 16-12:

TABLE 16-12 Example of a DMRS type 2 Number of co-scheduled Value CDMgroups UE rank Ports number of symbols X 3 3 0, 2, 4 1 Y 2 8 0, 1, 2, 3,6, 7, 8, 9 2

It should be noted that, the rules for SU scheduling that are providedin the foregoing embodiments do not limit specific port mapping. It maybe understood that, for specific different port mapping orders, numbersof different scheduled DMRS ports may be obtained by using a samescheduling rule. For example, when ports in the CDM group 1 are {0, 1,4, 5}, and ports in the CDM group 2 are {2, 3, 6, 7}, according to theFDM-first scheduling rule, six layers correspond to port numbers 0, 1,2, 3, 4, and 6. When ports in the CDM group 1 are {0, 1, 4, 6}, andports in the CDM group 2 are {2, 3, 5, 7}, according to the FDM-firstscheduling rule, six layers correspond to port numbers 0, 1, 2, 3, 4,and 5. It may be understood that, in cases of different port mappingorders, the foregoing two port number scheduling technologies are thesame in essence.

In summary, in the DMRS configuration information table provided in theembodiments of this application, CDM group information, or DMRS symbolinformation, or rate matching indication (RMI) information may be addedfor rate matching.

The following describes this in detail. Table 17-1 and Table 17-2 areDMRS port indication tables (DMRS port indication table) correspondingto different DMRS configurations (DMRS configuration types), where Table17-1 corresponds to a DMRS type 1, and Table 17-2 corresponds to a DMRStype 2. Herein, Table 17-1 and Table 17-2 each are divided into twocolumns based on a codeword number, to reduce bit overheads. Duringspecific implementation, a structure of the table may be designed inanother manner, and this is only an example.

In this embodiment, it is assumed that specific DMRS port mapping rulesof the DMRS type 1 and the DMRS type 2 are as follows:

for a 1-symbol DMRS type 1, ports included in a CDM group 1 are {0, 1},and ports included in a CDM group 2 are {2, 3};

for a 2-symbol DMRS type 1, ports included in a CDM group 1 are {0, 1,4, 5}, and ports included in a CDM group 2 are {2, 3, 6, 7};

for a 1-symbol DMRS type 2, ports included in a CDM group 1 are {0, 1},ports included in a CDM group 2 are {2, 3}, and ports included in a CDMgroup 3 are {4, 5}; and

for a 2-symbol DMRS type 2, ports included in a CDM group 1 are {0, 1,6, 7}, ports included in a CDM group 2 are {2, 3, 8, 9}, and portsincluded in a CDM group 3 are {4, 5, 10, 11}.

During specific implementation, there may be different DMRS port mappingrules. This embodiment is only for ease of description. Specifically,for different mapping rules, a scheduling rule in a table remainsunchanged.

It can be learned that, for each DMRS configuration, information about anumber of symbols of a DMRS and RMI information may be added to a table,to perform DMRS rate matching.

Optionally, herein, the RMI information that may be used for DMRS ratematching may be a number of CDM groups occupied in a current system, ora status of a combination of CDM groups occupied in a current system, ora sequence number of an occupied CDM group. The number of co-scheduledCDM groups provided in Table 17-1 and Table 17-2 are only examples. Fora method for obtaining the number of CDM groups or a method forobtaining a status of the combination of the occupied CDM groups, themethod in the foregoing embodiments may be used. For a manner ofobtaining a sequence number of an occupied CDM group, in oneimplementation method, when one CDM group is occupied, RMI in acorresponding table is “1”, and it indicates that a CDM group 1 isoccupied; when two CDM groups are occupied, RMI in a corresponding tableis “1, 2”, and it indicates that CDM groups 1 and 2 are occupied; orwhen three CDM groups are occupied, RMI in a corresponding table is “1,2, 3”, and it indicates that CDM groups 1, 2, and 3 are occupied. Duringspecific implementation, a correspondence between a quantity of occupiedCDM groups and sequence numbers of the CDM groups may change. This isonly an example.

Optionally, the DMRS symbol information is added to the table. In animplementation method, only a part of the table may be used duringspecific scheduling, to reduce DCI overheads. For example, when acurrent maximum number of symbols of a DMRS in the system is 1, duringspecific scheduling, a status corresponding to only one symbol, in otherwords, a status corresponding to a number of symbols being 1, isconfigured in the table. When the system informs that a current maximumnumber of symbols of a DMRS is 2, all statuses in the table areconfigured. The table configuration method may use the solution providedin the foregoing embodiments, for example, a part, for example, thestatus corresponding to the number of symbols being 1, of a table isselected by using independent RRC signaling. Alternatively, a tableconfiguration may be bound with signaling of a maximum number of symbolsof a DMRS. During specific implementation, the method in the foregoingembodiments may be used, and details are not repeated herein. In anotherimplementation method, the table may not include information about asymbol quantity of a DMRS, in other words, a number of symbols column.The DMRS symbol information is implicitly represented by using a value.For example, it may be predefined that in Table 17-1, values 0 to 10correspond to information about the 1-symbol DMRS type 1, and values 11to 34 correspond to information about 2-symbol DMRS type 1.

Optionally, a table may include a plurality of scheduling rules. Forexample, in Table 17-1, in a case of one codeword, a value 2 correspondsto that a current quantity of orthogonal ports (a quantity of layers) ofthe receive end is 2, where port numbers are 0 and 1, in other words,the CDM-first scheduling rule; and a value 35 corresponds to that acurrent quantity of orthogonal ports of the receive end is 2, where portnumbers are 0 and 2, in other words, the FDM-first scheduling rule.During specific implementation, states corresponding to both the value 2and the value 35 are reserved in the table, to satisfy schedulingflexibility. Alternatively, only a state corresponding to the value 35is reserved and a state corresponding to the value 2 is removed, toensure FDM-first scheduling for an SU. In this case, the receive end mayimplicitly learn, according to a port number scheduling rule, that acurrent state is an SU state. Alternatively, only a state correspondingto the value 2 is reserved and a state corresponding to the value 35 isremoved, to perform scheduling according to the CDM-first rule, therebyimproving spectral efficiency. Specifically, in Table 17-1, values 0 to34 correspond to a solution satisfying a basic scheduling requirement,and values 35 to 38 correspond to different scheduling methods. In animplementation method, the table may not include values 35 to 38, toreduce overheads. Alternatively, one or more of values 35 to 38 mayreplace one or more of values 0 to 34, to implement a particularscheduling requirement. Alternatively, one or more of values 35 to 38may be reserved in the table, to implement flexible scheduling.Similarly, in Table 17-2, in a case of two codewords, a value 24corresponds to a CDM-first scheduling rule when there are six layers, avalue 73 corresponds to a continuous DMRS-port-number scheduling schemewhen there are six layers, and a value 74 corresponds to an FDM-firstscheduling rule in two CDM groups when there are six layers. Duringspecific implementation, any one or more of the three schemes may bereserved, to satisfy a requirement of flexible scheduling or reducingoverheads. Specifically, in Table 17-2, values 0 to 70 correspond to asolution satisfying a basic scheduling requirement, and values 71 to 81correspond to different scheduling methods. During specificimplementation, the table may not include values 71 to 81, to reduceoverheads. Alternatively, one or more of values 71 to 81 may replace oneor more of values 0 to 70, for example, a state corresponding to thevalue 71 is reserved and a state corresponding to the value 2 is removedin a case of one codeword, to implement a particular schedulingrequirement. Alternatively, one or more of values 71 to 81 may bereserved in the table, to implement flexible scheduling. It may beunderstood that, the scheduling schemes provided in Table 17-1 and Table17-2 are only examples. During specific implementation, other schedulingschemes may be added to improve scheduling flexibility and satisfy ascheduling requirement.

Optionally, Table 17-1 and Table 17-2 provides a scheme in which DCIoverheads are reduced based on a codeword number. During specificimplementation, classification may not be performed based on thecodeword number, for example, a plurality of columns may be dividedbased on a quantity of layers of orthogonal ports (a quantity oforthogonal DMRS ports) of the receive end, to reduce DCI overheads.Alternatively, states corresponding to one codeword and two codewords inTable 17-1 (or Table 17-2) are grouped into different tables, tocorrespond to different bit overheads. Alternatively, statescorresponding to one codeword and two codewords in Table 17-1 (or Table17-2) are encoded together. For example, values 0 to 38 in Table 17-1correspond to a state in which a quantity of orthogonal layers of thereceive end is less than or equal to 4, and values greater than or equalto 39 correspond to a state in a case of two codewords in Table 17-1 (aquantity of orthogonal layers of the receive end is greater than 4). Foran implementation method, refer to Table 17-3 and Table 17-4. Inspecific implementation, a state indication sequence may be changed, orsome items may be replaced or removed, to implement different schedulingrequirements. Alternatively, it may be configured that some states inthe table are used in specific scheduling to reduce overheads. For aspecific implementation method, refer to the foregoing embodiments. Inaddition, the table may include indications of SU and MU states, asshown in content in parentheses in Table 17-3 and Table 17-4. It may beunderstood that, during specific implementation, indication informationof the SU and MU states may not be included, and a possibleimplementation method is provided herein.

TABLE 17-1 Example of a DMRS port combination type 1 One Codeword (≤4layers) Two Codewords (>4 layers) RMI RMI (number (number of co- of co-scheduled number scheduled number CDM of CDM of Value groups) UE rankPorts symbols Value groups) UE rank Ports symbols 0 1 1 0 1 0 reservedreserved reserved 1 1 1 1 1 1 1 reserved reserved reserved 1 2 1 2 0, 11 2 reserved reserved reserved 1 3 2 1 0 1 3 reserved reserved reserved1 4 2 1 1 1 4 reserved reserved reserved 1 5 2 1 2 1 5 reserved reservedreserved 1 6 2 1 3 1 6 reserved reserved reserved 1 7 2 2 0, 1 1 7reserved reserved reserved 1 8 2 2 2, 3 1 8 reserved reserved reserved 19 2 3 0-2 1 9 reserved reserved reserved 1 10 2 4 0-3 1 10 reservedreserved reserved 1 11 1 1 0 2 11 2 5 0-2, 4, 5 2 12 1 1 1 2 12 2 6 0-52 13 1 1 4 2 13 2 7 0-6 2 14 1 1 5 2 14 2 8 0-7 2 15 1 2 0, 1 2 15reserved reserved reserved 2 16 1 2 4-5 2 16 reserved reserved reserved2 17 1 3 0, 1, 4 2 17 reserved reserved reserved 2 18 1 4 0, 1, 4, 5 218 reserved reserved reserved 2 19 2 1 0 2 19 reserved reserved reserved2 20 2 1 1 2 20 reserved reserved reserved 2 21 2 1 2 2 21 reservedreserved reserved 2 22 2 1 3 2 22 reserved reserved reserved 2 23 2 1 42 23 reserved reserved reserved 2 24 2 1 5 2 24 reserved reservedreserved 2 25 2 1 6 2 25 reserved reserved reserved 2 26 2 1 7 2 26reserved reserved reserved 2 27 2 2 0, 1 2 27 reserved reserved reserved2 28 2 2 2, 3 2 28 reserved reserved reserved 2 29 2 2 4, 5 2 29reserved reserved reserved 2 30 2 2 6, 7 2 30 reserved reserved reserved2 31 2 3 0, 1, 4 2 31 reserved reserved reserved 2 32 2 3 2, 3, 6 2 32reserved reserved reserved 2 33 2 4 0, 1, 4, 5 2 33 reserved reservedreserved 2 34 2 4 2, 3, 6, 7 2 34 reserved reserved reserved 2 35 2 2 0,2 1 35 2 5 0-4 2 36 2 2 0, 2 2 36 2 6 0-4, 6 2 37 2 3 0-2 2 37 reservedreserved reserved reserved 38 2 4 0-3 2 38 reserved reserved reservedreserved

TABLE 17-2 Example of a DMRS port combination type 2 One Codeword (≤4layers) Two Codewords (>4 layers) RMI RMI (number (number of co- of co-scheduled number scheduled number CDM of CDM of Value groups) UE rankPorts symbols Value groups) UE rank Ports symbols 0 1 1 0 1 0 3 5 0-4 11 1 1 1 1 1 3 6 0-5 1 2 1 2 0, 1 1 2 reserved reserved reserved 1 3 2 10 1 3 reserved reserved reserved 1 4 2 1 1 1 4 reserved reservedreserved 1 5 2 1 2 1 5 reserved reserved reserved 1 6 2 1 3 1 6 reservedreserved reserved 1 7 2 2 0, 1 1 7 reserved reserved reserved 1 8 2 2 2,3 1 8 reserved reserved reserved 1 9 2 3 0-2 1 9 reserved reservedreserved 1 10 2 4 0-3 1 10 reserved reserved reserved 1 11 3 1 0 1 11reserved reserved reserved 1 12 3 1 1 1 12 reserved reserved reserved 113 3 1 2 1 13 reserved reserved reserved 1 14 3 1 3 1 14 reservedreserved reserved 1 15 3 1 4 1 15 reserved reserved reserved 1 16 3 1 51 16 reserved reserved reserved 1 17 3 2 0, 1 1 17 reserved reservedreserved 1 18 3 2 2, 3 1 18 reserved reserved reserved 1 19 3 2 4, 5 119 reserved reserved reserved 1 20 3 3 0-2 1 20 reserved reservedreserved 1 21 3 3 3-5 1 21 reserved reserved reserved 1 22 3 4 0-3 1 22reserved reserved reserved 1 23 1 1 0 2 23 2 5 0-2, 6, 7 2 24 1 1 1 2 242 6 0-3, 6, 7 2 25 1 1 6 2 25 2 7 0-3, 6-8 2 26 1 1 7 2 26 2 8 0-4, 6-92 27 1 2 0, 1 2 27 reserved reserved reserved 2 28 1 2 6, 7 2 28reserved reserved reserved 2 29 1 3 0, 1, 6 2 29 reserved reservedreserved 2 30 1 4 0, 1, 6, 7 2 30 reserved reserved reserved 2 31 2 1 02 31 reserved reserved reserved 2 32 2 1 1 2 32 reserved reservedreserved 2 33 2 1 2 2 33 reserved reserved reserved 2 34 2 1 3 2 34reserved reserved reserved 2 35 2 1 6 2 35 reserved reserved reserved 236 2 1 7 2 36 reserved reserved reserved 2 37 2 1 8 2 37 reservedreserved reserved 2 38 2 1 9 2 38 reserved reserved reserved 2 39 2 2 0,1 2 39 reserved reserved reserved 2 40 2 2 2, 3 2 40 reserved reservedreserved 2 41 2 2 6, 7 2 41 reserved reserved reserved 2 42 2 2 8, 9 242 reserved reserved reserved 2 43 2 3 0, 1, 6 2 43 reserved reservedreserved 2 44 2 3 2, 3, 8 2 44 reserved reserved reserved 2 45 2 4 0, 1,6, 7 2 45 reserved reserved reserved 2 46 2 4 2, 3, 8, 9 2 46 reservedreserved reserved 2 47 3 1 0 2 47 reserved reserved reserved 2 48 3 1 12 48 reserved reserved reserved 2 49 3 1 2 2 49 reserved reservedreserved 2 50 3 1 3 2 50 reserved reserved reserved 2 51 3 1 4 2 51reserved reserved reserved 2 52 3 1 5 2 52 reserved reserved reserved 253 3 1 6 2 53 reserved reserved reserved 2 54 3 1 7 2 54 reservedreserved reserved 2 55 3 1 8 2 55 reserved reserved reserved 2 56 3 1 92 56 reserved reserved reserved 2 57 3 1 10  2 57 reserved reservedreserved 2 58 3 1 11  2 58 reserved reserved reserved 2 59 3 2 0, 1 2 59reserved reserved reserved 2 60 3 2 2, 3 2 60 reserved reserved reserved2 61 3 2 4, 5 2 61 reserved reserved reserved 2 62 3 2 6, 7 2 62reserved reserved reserved 2 63 3 2 8, 9 2 63 reserved reserved reserved2 64 3 2 10, 11 2 64 reserved reserved reserved 2 65 3 3 0, 1, 6 2 65reserved reserved reserved 2 66 3 3 2, 3, 8 2 66 reserved reservedreserved 2 67 3 3 4, 5, 10 2 67 reserved reserved reserved 2 68 3 4 0,1, 6, 7 2 68 reserved reserved reserved 2 69 3 4 2, 3, 8, 9 2 69reserved reserved reserved 2 70 3 4 4, 5, 10, 11 2 70 reserved reservedreserved 2 71 2 2 0, 2 1 71 3 5 0-4 2 72 3 3 0, 2, 4 1 72 2 5 0-3, 6 273 3 4 0-2, 4  1 73 3 6 0-5 2 74 2 2 0, 2 2 74 3 6 0-3, 6, 8 2 75 3 3 0,2, 4 2 75 3 7 0-6 2 76 2 4 0, 1, 2, 3 2 76 3 8 0-6, 8 2 77 3 4 0, 1, 2,4 2 77 3 8 0-7 2 78 3 3 2, 3, 7 2 78 reserved reserved reserved reserved79 3 3 8, 9, 4 2 79 reserved reserved reserved reserved 80 3 3 10, 11, 52 80 reserved reserved reserved reserved 81 3 3 7, 9, 11 2 81 reservedreserved reserved reserved

TABLE 17-3 Example of a DMRS port combination type 1 number RMI (numberof co- of Value scheduled CDM groups) UE rank Ports symbols 0 1 1 0 1 11 1 1 1 2 1 2 0, 1 (SU) 1 3 2 1 0 1 4 2 1 1 1 5 2 1 2 1 6 2 1 3 1 7 2 20, 1 1 8 2 2 2, 3 1 9 2 3 0-2 (SU) 1 10 2 4 0-3 (SU) 1 11 2 2 0, 2 (SU)1 12 1 1 0 2 13 1 1 1 2 14 1 1 4 2 15 1 1 5 2 16 1 2 0, 1 (SU/MU) 2 17 12 4-5 2 18 1 3 0, 1, 4 (SU/MU) 2 19 1 4 0, 1, 4, 5 (SU) 2 20 2 1 0 2 212 1 1 2 22 2 1 2 2 23 2 1 3 2 24 2 1 4 2 25 2 1 5 2 26 2 1 6 2 27 2 1 72 28 2 2 0, 1 2 29 2 2 2, 3 2 30 2 2 4, 5 2 31 2 2 6, 7 2 32 2 3 0, 1, 42 33 2 3 2, 3, 6 2 34 2 4 0, 1, 4, 5 2 35 2 4 2, 3, 6, 7 2 36 2 5 0-2,4, 5 (SU) 2 37 2 6 0-5 (SU) 2 38 2 7 0-6 2 39 2 8 0-7 2 40 2 5 0-4 (SU)2 41 2 6 0-4, 6 (SU) 2 42 2 2 0, 2 (SU) 2 43 2 3 0-2 (SU) 2 44 2 4 0-3(SU) 2

TABLE 17-4 Example of a DMRS port combination type 2 RMI (number of co-number of Value scheduled CDM groups) UE rank Ports symbols 0 1 1 0 1 11 1 1 1 2 1 2 0, 1 (SU) 1 3 2 1 0 1 4 2 1 1 1 5 2 1 2 1 6 2 1 3 1 7 2 20, 1 1 8 2 2 2, 3 1 9 2 3 0-2 (SU/MU) 1 10 2 4 0-3 (SU) 1 11 3 1 0 1 123 1 1 1 13 3 1 2 1 14 3 1 3 1 15 3 1 4 1 16 3 1 5 1 17 3 2 0, 1 1 18 3 22, 3 1 19 3 2 4, 5 1 20 3 3 0-2 1 21 3 3 3-5 1 22 3 4 0-3 1 23 3 5 0-4 124 3 6 0-5 1 25 2 2 0, 2 (SU) 1 26 3 3 0, 2, 4 (SU) 1 27 3 4 0-2, 4 (SU)1 28 1 1 0 2 29 1 1 1 2 30 1 1 6 2 31 1 1 7 2 32 1 2 0, 1 (SU/MU) 2 33 12 6, 7 2 34 1 3 0, 1, 6 2 35 1 4 0, 1, 6, 7 (SU) 2 36 2 1 0 2 37 2 1 1 238 2 1 2 2 39 2 1 3 2 40 2 1 6 2 41 2 1 7 2 42 2 1 8 2 43 2 1 9 2 44 2 20, 1 2 45 2 2 2, 3 2 46 2 2 6, 7 2 47 2 2 8, 9 2 48 2 3 0, 1, 6 2 49 2 32, 3, 8 2 50 2 4 0, 1, 6, 7 2 51 2 4 2, 3, 8, 9 2 52 3 1 0 2 53 3 1 1 254 3 1 2 2 55 3 1 3 2 56 3 1 4 2 57 3 1 5 2 58 3 1 6 2 59 3 1 7 2 60 3 18 2 61 3 1 9 2 62 3 1 10 2 63 3 1 11 2 64 3 2 0, 1 2 65 3 2 2, 3 2 66 32 4, 5 2 67 3 2 6, 7 2 68 3 2 8, 9 2 69 3 2 10, 11 2 70 3 3 0, 1, 6 2 713 3 2, 3, 8 2 72 3 3 4, 5, 10 2 73 3 4 0, 1, 6, 7 2 74 3 4 2, 3, 8, 9 275 3 4 4, 5, 10, 11 2 76 2 5 0-2, 6, 7 (SU) 2 77 2 6 0-3, 6, 7 (SU) 2 782 7 0-3, 6-8 (SU) 2 79 2 8 0-4, 6-9 (SU) 2 80 3 5 0-4 (SU) 2 81 2 5 0-3,6 (SU) 2 82 3 6 0-5 (SU) 2 83 3 6 0-3, 6, 8 (SU) 2 84 3 7 0-6 (SU) 2 853 8 0-6, 8 (SU) 2 86 3 8 0-7 (SU) 2 87 2 2 0, 2 (SU) 2 88 3 3 0, 2, 4(SU) 2 89 2 4 0, 1, 2, 3 (SU) 2 90 3 4 0, 1, 2, 4 (SU) 2 91 3 3 2, 3, 7(MU) 2 92 3 3 8, 9, 4 (MU) 2 93 3 3 10, 11, 5 (MU) 2 94 3 3 7, 9, 11(MU) 2

In LTE, in a case of MU-MIMO, a maximum of four orthogonal ports aresupported. These ports use a same RE resource. A benefit of such adesign is that a DMRS rate matching (RM) problem can be effectivelyavoided in the case of MU-MIMO. Simply, rate matching means that theterminal needs to know REs on which no data transmission is performed ona time-frequency resource of the terminal, to keep off these REs duringdata demodulation and correctly decode data. For example, duringdownlink transmission, some REs on the time-frequency resource of theterminal may be occupied by a control channel or an RS. If the basestation does not notify the terminal of information about locations ofthe REs, the terminal uses REs or control information on the locationsas data and performs demodulation, leading to a decoding error.

In a single-user multiple-input multiple-output (SU-MIMO) scenario, thebase station communicates with only one terminal, and transmits onlyinformation (an RS, control signaling, data, or the like) of theterminal on a time-frequency resource. In this case, the terminal candirectly learn of locations of DMRS REs of the terminal based on theinformation of the terminal (for example, a port, a quantity of layers,or the like of the terminal), and avoid the REs during data decoding.Therefore, there is no DMRS rate matching problem in the SU scenario.

In a multi-user multiple-input multiple-output (MU-MIMO), the basestation communicates with a plurality of terminals, orthogonalitybetween terminals is ensured by using an orthogonal DMRS port, andorthogonality between ports may be ensured through time divisionmultiplexing (TDM), frequency division multiplexing (FDM), or codedivision multiplexing (CDM). When TDM and FDM are used, orthogonal DMRSports occupy different time-frequency resources. In this case, data ofother DMRS ports cannot be transmitted on REs occupied by the DMRSports. For example, a port 1 and a port 2 are orthogonal through FDM orTDM, and the port 1 occupies an RE 1. In this case, the base stationdoes not transmit data of the port 2 on the RE 1, to prevent the data ofthe port 2 from causing noise interference to a DMRS of the port 1 andavoid affecting channel estimation precision. However, when the port 1and port 2 are orthogonal through CDM, the foregoing problem does notexist. This is because although the DMRS of the port 1 and a DMRS ofport 2 occupy a same RE, the two ports performs multiplexing in a codedivision multiplexing mode, thereby ensuring orthogonality between theDMRSs of the two ports.

During MU-MIMO, the terminal needs to know port information of anotherterminal that is co-scheduled, to learn of RE locations that areoccupied by DMRSs on ports used by the another terminal and at which nodata of the terminal is transmitted. If the terminal cannot learn of theinformation, the terminal uses a DMRS from another user as the data ofthe terminal for decoding, leading to a decoding error.

In LTE, a rate matching problem in MU-MIMO is resolved by ensuring thatDMRSs of scheduled ports are multiplexed through CDM. In this case,DMRSs of all terminals are multiplexed on a same RE through CDM, therebyavoiding a DMRS rate matching problem. Such a design may be referred toas MU-MIMO transparent to a terminal. However, as described above, inLTE, to ensure this transparent design, MU-MIMO can support only amaximum of four orthogonal ports.

In an NR system, for example, 5G, to fully take the advantage ofMU-MIMO, a design in which MU-MIMO supports a maximum of 12 orthogonalports has been used in a standard. Considering that a DMRS pattern in anexisting standard can support CDM multiplexing of only a maximum of fourports, the transparent solution in LTE is no longer applicable.

Therefore, such a new MU-MIMO DMRS rate matching design is veryimportant, and DMRS rate matching can be resolved in the followingmanners:

In a first manner, no data is transmitted in all subcarriers on alocation of a resource unit, for example, a symbol, corresponding to aDMRS. Such a solution does not require a signaling indication, butcauses a relatively great waste of spectrum resources. For example, inFIG. 20, UE 0 uses a port 1 to a port 4, UE 1 uses a port 5 to a port 8,and no data is transmitted on REs corresponding to locations of a port 9to a port 12. This causes a great resource waste.

In a second manner, UE is directly notified of a port sequence number ofanother UE. When the another UE occupies relatively more ports,relatively high signaling overheads are caused. For example, when UE 0uses ports 1 and 2, and UE 1 uses a port 5 to a port 8, the UE 0 needsto be notified of the ports 5 to 8 used by the UE 1, and the UE 1 needsto be notified of the ports 1 and 2 used by the UE 0. This mannerrequires particularly high signaling overheads.

Specifically, a I/O bit map is required to indicate an absolute locationof a DMRS port. For example, each DMRS port group in FIG. 34 isseparately indicated by using one bit, for six port groups included inFIG. 20, six bits need to be used to indicate an actual sending layerquantity, and a port allocation rule is used for constraint, forexample, to directly indicate a quantity of layers scheduled by acurrent base station. For FIG. 20, there is a possibility that one layerto 12 layers need to be separately indicated, and four bits are requiredfor indication.

To implement more effective data transmission, this application providesa rate matching indication solution corresponding to a maximum supportedport quantity, a DMRS pattern or a CDM port group quantity in thepattern, or a DMRS configuration type, to match a 5G DMRS transmissionrequirement.

The following describes a DMRS rate matching indicating and receivingmethod provided in this application.

FIG. 21 shows a demodulation reference signal rate matching indicatingand receiving method provided in this application. The method mayinclude the following steps.

S201. A transmit end generates demodulation reference signal (DMRS)indication information, where the DMRS indication information is used toindicate a resource that is not occupied by DMRS and that is inresources available for carrying a DMRS.

The DMRS indication information indicates a current quantized quantityof orthogonal transmission layers, a combination of currently used portgroup states, an orthogonal-transmission-layer quantity or a port groupstate that is not currently used by a receive end, or a resource unitthat needs to be muted, to indicate the resource that is not occupied byDMRS and that is in the resources available for carrying a DMRS.

In an implementation, before the transmit end sends the DMRS indicationinformation, the method further includes: sending DMRS transmissionscheme indication information, to indicate the current DMRS transmissionscheme, where different DMRS transmission schemes correspond todifferent maximum supported orthogonal-port quantities, or correspond todifferent DMRS patterns or different DMRS configuration types.

Specifically, different maximum supported port quantities, or DMRSpatterns (or CDM port group quantities in DMRS patterns), or DMRSconfiguration types are indicated by using different DMRS indicationinformation. For example, in an MU-MIMO scenario in which maximumsupported orthogonal-port quantities are 4, 6, 8, and 12, or maximumsupported non-orthogonal-port quantities are 8, 12, 16, and 24respectively, all of these maximum supported port quantities havingcorresponding DMRS rate matching information, and at least two of theseDMRS rate matching states are different.

The DMRS indication information is used to inform the receive end of arate matching status, in other words, on a time-frequency resource,which resource units have not been occupied by DMRSs of other receiveends but are used for data transmission. The receive end may correctlydecode data on these resource units during data demodulation.

In another implementation, the DMRS indication information is configuredfor different DMRS patterns or a quantity of DMRS port groups includedin a DMRS pattern (for example, there may be two tables respectivelycorresponding to DMRS patterns that include two or three DMRS portgroups). Usually, one DMRS pattern corresponds to one MU-MIMO scenariosupporting a maximum supported orthogonal-port quantity. The DMRSpattern shows a quantity of orthogonal CDM port groups supported by theMU-MIMO scenario and a quantity of resource units included in each portgroup. Therefore, different indication information is configured fordifferent DMRS patterns. Alternatively, the receive end may indication,on a time-frequency resource, which resource units have not been usedfor DMRS transmission, but are used for data transmission. The receiveend may correctly decode data.

In still another implementation, the DMRS indication information may befurther configured for a DMRS configuration type.

During specific implementation, for ease of description in thisembodiment of this application, the DMRS indication information may berepresented by using a value. During specific implementation, the DMRSindication information may be N bits, where N is related to a quantity M(CS/OCC/CS+OCC) of DMRS port groups included in a DMRS pattern. Fordifferent patterns or DMRS configuration types (type), values of N maybe different. For example, for a DMRS configuration type 1 including twoDMRS port groups (M=2), N may be 1 or 2; and for a DMRS configurationtype 2 including three DMRS port groups (M=3), N may be 2 or 3.

As shown in the following Table 18, this is an example of the DMRSindication information. The DMRS indication information in thisembodiment is mainly used for rate matching, and therefore, isrepresented as rate matching indication information. A specific form isnot limited to the following forms, and may be a table, a digit, or aformula. The DMRS indication information has P states, where a value ofP may be represented by using N bits (all signaling states), or morethan N bits (increasing system scheduling flexibility or satisfyingother design requirement), or less than N bits (quantizing to reducesignaling overheads). M_p is rate matching information (RMI) or aparameter set including DMRS rate matching information. The terminal maycomplete DMRS-related rate matching according to an indication of Mp.The rate matching information is represented by RMI in subsequentdescriptions and drawings only for ease of description, and no limit isimposed on a meaning thereof. During specific implementation, the ratematching information may be indicated by using a quantized value of aquantity of orthogonal transmission layers, or may be indicated by usingthe foregoing methods such as using the port number or using the CDMgroup.

TABLE 18 DMRS indication information (also referred to as rate matchingindication information) Rate (value) matching information, RMI 0 M_0 . .. . . . P M_P

The rate matching indication information is related to the rate matchinginformation. When the rate matching information may be represented byusing a specific quantity of orthogonal transmission layers, the DMRSindication information is determined in the DMRS configurationinformation. The DMRS configuration information further includesindication information of a total quantity of orthogonal ports, and theindication information for the total quantity of orthogonal ports mayindicate a quantity of all orthogonal ports that are possibly actuallypresented or a quantized value of a quantity of all orthogonal portsthat are possibly actually presented. The quantized value of thequantity of all the orthogonal ports is information about a quantity oforthogonal DMRS layers, indication information of an orthogonal DMRSantenna port set, CDM group information of an orthogonal DMRS antennaport, or information generated based on a CDM group size.

During specific implementation, the quantized value of the quantity oforthogonal transmission layers may be about a quantity of DMRS layers,DMRS antenna port set information, or DMRS antenna port CDM groupinformation. In the information about the quantity of DMRS layers, thequantity of DMRS layers may be an integer multiple of a quantity of DMRSantenna ports in a CDM group. For example, for a DMRS pattern includingtwo DMRS antenna port groups, assuming that a port group 1 is {1, 2, 3,4}, and a port group 2 is {5, 6, 7, 8}, the port group 1 and the portgroup 2 may be quantized into four layers and eight layers. In addition,in the information about the quantity of DMRS layers, the quantity ofDMRS layers may alternatively be an integer multiple of a quantity ofDMRS antenna ports having consecutive sequence numbers in ascendingorder in a CDM group. For example, CDM groups {1, 2, 5, 7} and {3, 4, 6,8} may be quantized into two layers and four layers. All of theinformation can enable the receive end to identify which resource unitsare used for DMRS transmission at the receive end and which resourceunits are used for DMRS transmission at other receive ends thatimplement CDM multiplexing. Remaining resource units are used for datatransmission related to the receive end. Therefore, the receive enddemodulates data on a corresponding resource unit.

It should be understood that, content of the rate matching informationmay vary with a port mapping order in a DMRS pattern, for example, mayinclude but is not limited to:

1. A muted state or a used state of a DMRS port group: The rate matchinginformation indicates a state of each DMRS port group, and the contentof the RMI is unrelated to a port mapping order. There is no specificlimit on a numbering sequence in a CDM group. For example, ports may benumbered in ascending order from a smallest sequence number of a port ina port group.

2. Current quantity of orthogonal transmission layers of a system thatare quantized through grading

It is assumed that a DMRS port number is p=y+v, where y is a port numberoffset, it can be ensured that p is a minimum DMRS port value defined inNR, and v=1, 2, . . . , and is a current quantity of orthogonaltransmission layers (eight ports in LTE) on a PDSCH. v is quantizedthrough grading, to reduce DCI signaling overheads for rate matching.During specific implementation, v may be quantized upward or downward.

2.1. A total current quantity of layers of the system that is quantizedupward through grading (where the content of the rate matchinginformation is related to a mapping order): which may be equal to aquantity of continuous port numbers or a maximum port sequence number ineach CDM group (assuming that y=0 and only when port numbers in each CDMgroup are continuous and in ascending order or descending order). Forexample, when a mapping order of {1, 2, 3, 4}, {5, 6, 7, 8}, and {9, 10,11, 12} changes, for a same DMRS pattern, the content of the RMIchanges.

2.2. A total current quantity of orthogonal transmission layers of thesystem is quantized downward through grading: In this manner, thecontent of the rate matching information is unrelated to a mapping orderin a DMRS pattern, and the content may be equal to a smallest portnumber in continuous port numbers in a CDM group, or may be a quantizedvalue of a port number numbered from 1 (assuming that y=0, and ports arenumbered from 1).

2.3. A quantity of continuous DMRS numbers when port numbers in a DMRSgroup are sorted in ascending order: For example, two DMRS port groups{1, 2, 5, 6} and {3, 4, 7, 8} may be quantized into two layers and fourlayers.

It should be noted that, a reason for using a quantized value of aquantity of orthogonal DMRS transmission layers is that, for example, ifspecific orthogonal-transmission-layer quantities {1, 2, 3, 4} need tobe indicated, two bits are needed for indication. When theorthogonal-transmission-layer quantities {1, 2, 3, 4} are quantized intoa value, for example, quantized upward into anorthogonal-transmission-layer quantity 4, or quantized downward into anorthogonal-transmission-layer quantity 1, or when theorthogonal-transmission-layer quantities {1, 2, 3, 4} are represented by2 or 3, only one bit is required to indicate the quantized value of thequantity of orthogonal transmission layers. For example, 0 is used torepresent a quantized value 4 of the orthogonal-transmission-layerquantity. Therefore, indication overheads can be reduced.

2.4. The DMRS group state information, the DMRS group sequence number orgroup number, or the DMRS group quantity: The number of CDM groups is aquantity of CDM groups occupied/scheduled (co-scheduled) in the system.

S202. The transmit end sends the DMRS indication information on atime-frequency resource.

During specific implementation, in this embodiment of this application,the DMRS indication information may be used to indicate differentmaximum supported port quantities or rate matching manners correspondingto different DMRS patterns. One manner is implicit indication, andanother manner is indication by using explicit signaling.

In the implicit indication solution, the quantized value of the quantityof orthogonal transmission layers is configured in a DMRS configurationinformation table, and the indication information is indicated by usingDMRS indication information (a value) in the DMRS configurationinformation table. The DMRS configuration information table may besimilar to that in LTE. For example, the DMRS indication information isa quantity of antenna ports, a scrambling identification, and anindication of a quantity of orthogonal transmission layers (number oflayers indication) in LTE. The DMRS configuration information table mayfurther include at least one of a DMRS port quantity, a port index,sequence generation information, and a CDM type. Based on this, thequantized value of the quantity of orthogonal transmission layers isadded. The DMRS configuration information table may be stored at boththe transmit end and the receive end. The transmit end sends theindication information to the receive end. It should be understood that,the transmit end sends original DCI signaling in LTE (because thesignaling in LTE is used, the DCI signaling may not be named asindication information, but may indicate a rate matching solution) tothe receive end. The receive end obtains, by using the signaling, portinformation of the receive end and a total quantized quantity oftransmission layers in a system, and calculates, with reference to thetwo pieces of information, a port used by another receive end. In otherwords, the receive end identifies which resource units are used for DMRStransmission at the receive end and which resource units are used forDMRS transmission at other receive ends that implement CDM multiplexing.Remaining resource units are used for data transmission related to thereceive end. Therefore, the receive end demodulates data on acorresponding resource unit.

In the explicit signaling indication solution, a correspondence betweenthe DMRS indication information and the rate matching information existsindependently of a DMRS configuration information table in LTE. In otherwords, the correspondence between the DMRS indication information andthe rate matching information is not implied in the DMRS configurationinformation table. Therefore, in addition to the DMRS configurationinformation table, the transmit end and the receive end furtherseparately store a correspondence configuration table between the DMRSindication information and the rate matching information (or theinformation table may be configured through RRC). The correspondenceconfiguration table exists independently of the DMRS configurationinformation table. The transmit end sends rate configuration indicationinformation to the receive end by using implicit signaling. The receiveend uses the DMRS indication information as an index, and searches thecorrespondence configuration table for corresponding rate matchinginformation. The receive end combines the rate matching information withthe DMRS configuration information table, to identify which resourceunits are occupied by the DMRS of the receive end, and which resourceunits are occupied by DMRSs of other receive ends that implement CDMmultiplexing. Remaining resource units are used for data transmissionrelated to the receive end. Therefore, the receive end demodulates dataon a corresponding resource unit.

It should be noted that DMRS indication information having a same valuemay correspond to quantized values of different quantities of orthogonaltransmission layers. Therefore, the correspondence between the DMRSindication information and the quantized value of the quantity oforthogonal transmission layers may alternatively be indicated throughseparate signaling. It should be understood that, in the explicitindication solution, the quantized quantity of orthogonal transmissionlayers is indicated by using the DMRS indication information. Thereceive end receives two pieces of signaling, where one piece ofsignaling is DMRS DCI signaling in LTE, and the other piece of signalingis signaling (which may also be referred to as rate matching signalingin this specification) used to transmit DMRS indication information of acurrent quantized quantity of orthogonal transmission layers orincluding DMRS indication information.

It may be understood that, regardless of the implicit indicationsolution or the explicit indication solution, the DMRS indicationinformation may be sent to the receive end as independent signaling ormay be carried in downlink signaling for sending. This is not limitedherein.

The foregoing signaling for sending the DMRS indication information andindicating the correspondence between the DMRS indication informationand the quantized value of the quantity of orthogonal transmissionlayers may be radio resource control (RRC) signaling, a media accesscontrol control element (MAC CE) or DCI signaling, or a combination ofany two or more of the three pieces of signaling.

In an implementation, whether to send the DMRS indication information byusing the signaling is determined based on a quantity of codewords. Forexample, in a case of one codeword, signaling is triggered to send theDMRS indication information, but in a case of two codewords, thesignaling is not sent. This is because in an SU-MIMO scenariocorresponding to the two codewords, when the transmit end, for example,a base station, communicates with only one receive end (a terminal),only information (RS, control signaling, data, or the like) of theterminal is transmitted on a time-frequency resource. In this case, theterminal can directly learn of locations of DMRS REs of the terminalbased on the information of the terminal (for example, a port, aquantity of layers, or the like of the terminal), and avoid the REsduring data decoding. Therefore, there is no DMRS rate matching problemin the SU scenario.

S203. A receive end receives the DMRS indication information.

S204. Obtain rate matching information based on the DMRS indicationinformation, and demodulate data on a resource on which no DMRS istransmitted.

During specific implementation, if the implicit indication manner isused, after receiving the DMRS indication information, the receive enduses a value of the DMRS indication information as an index, to searchthe DMRS configuration information table for information such as thequantized value of the corresponding quantity of orthogonal transmissionlayers (further, to learn of information about the quantity of DMRSlayers, the DMRS antenna port set information, the DMRS antenna portcode division multiplexing CDM group information, or the like), aquantity of layers used by the receive end, and the DMRS port number.Then, the receive end identifies which resource units are used for DMRStransmission at the receive end and which resource units are used forDMRS transmission at other receive ends that implement CDM multiplexing.Remaining resource units are used for data transmission related to thereceive end. Therefore, the receive end demodulates data on acorresponding resource unit. If the explicit indication manner is used,in addition to the DMRS configuration information table, when thetransmit end and the receive end further separately store thecorrespondence configuration table (or the correspondence configurationtable may be configured through RRC), the receive end uses theindication information as an index, to search the correspondenceconfiguration table for a corresponding rate matching state. The receiveend combines the rate matching information with the DMRS configurationinformation table, to identify which resource units are used by thereceive end for DMRS transmission, and which resource units are used byother receive ends for DMRS transmission (where optionally, in animplementation method, the information may be directly obtained by usingthe rate matching information). The remaining resource units are usedfor data transmission related to the receive end. Therefore, the receiveend demodulates data on a corresponding resource unit.

The DMRS indicating and receiving method provided in this applicationmay be further applied to a non-coherent joint transmission (NC-JT)2-PDCCH scenario. Specifically, two transmit ends using non-quasico-location QCL groups each transmit data after muting a resource unitcorresponding to a DMRS that is not of the transmit end. It may beunderstood as that, the transmit ends mutually mute a DMRS port group ofthe peer party. During specific implementation, it may be that a TRPmutes, by default, an RE location corresponding to a DMRS in a QCL groupof a peer TRP. For a DMRS pattern type 1, two DMRS port groups areincluded. In an NC-JT scenario, two DMRS port groups may be non-QCL, andports in each of the DMRS port groups are QCL. In this case, two TRPsmay separately use one port group. Therefore, this solution can directlyresolve the problem without extra signaling indication. For a DMRSpattern type 2, three DMRS port groups are included. In this case, oneTRP may use one DMRS port group, and the other TRP may use two DMRS portgroups. Therefore, the TPR using the two DMRS port groups needs toperform indication by using indication information, and the TPR usingthe DMRS port group may perform indication by using no indicationinformation.

In a 1-PDCCH scenario, an independent indication manner mayalternatively be used. For a specific procedure, still refer to thesteps shown in FIG. 21.

It should be noted that in step S201, a non-coherent joint transmissiontransmit end generates DMRS indication information, where the DMRSindication information is generated based on DMRS ports in a QCL groupavailable for a plurality of coordinating TRPs.

In step S202, the transmit end sends the DMRS indication information toa receive end. In the 1-PDCCH scenario, the DMRS indication informationindicates a resource unit corresponding to a DMRS available for aplurality of coordinating TRPs. In the 2-PDCCH scenario, the ratematching information indicates a resource unit corresponding to a DMRSused by the transmit end.

Operations performed after the receive end receives the DMRS indicationinformation are the same as S203 and S204 in the foregoing embodiment,and details are not described herein again.

If the technical solution is applied to an uplink transmission scenario,the transmit end may be a terminal, and the receive end may be a networkdevice, for example, a base station. If the technical solution isapplied to a downlink transmission scenario, the transmit end may be anetwork device, for example, a base station, and the receive end may bea terminal.

According to the DMRS rate matching indicating method provided in thisapplication, the DMRS indication information corresponds to the maximumsupported port quantity, the DMRS pattern, or the DMRS configurationtype, so as to match a plurality of scenarios in NR, for example, anNC-JT scenario, a dynamic TDD scenario, or a flexible duplex scenario.The foregoing method can be applied to complex and variable scenarios inNR, and can also satisfy a requirement for transmitting more layers ofdata and reduce indication overheads.

It may be understood that, the DMRS port herein is all DMRS portssupported by the system. During actual implementation, whether all orsome of the DMRS ports are used in one scheduling process is not limitedin this application.

The following describes a specific implementation process of the DMRSrate matching indicating method and the DMRS rate matching receivingmethod provided in this application.

Embodiment 5

Embodiment 5 mainly describes that explicit signaling is designed toindicate DMRS indication information.

As shown in FIG. 22, a TRP 0 supports a maximum supportedorthogonal-port quantity of 12, where ports allocated to a terminal 0(UE 0) are ports 1, 2, 7, and 8, and ports allocated to a terminal 1(UE 1) are ports 3, 4, 9, and 10.

In this scenario, the UE 0 and the UE 1 use a plurality of DMRS ports.FIG. 23 is a schematic diagram of a mapping rule of 12 DMRS ports, whereeach shaded box indicates an RE to which one DMRS port group is mapped,and n=0. The 12 DMRS ports are grouped into three DMRS port groups: aDMRS port group 1, a DMRS port group 2, and a DMRS port group 3.

Each DMRS port group includes four DMRS ports. A same time-frequencyresource is multiplexed through CDM for DMRSs corresponding to the DMRSports in each DMRS port group. A mapping rule of the three DMRS portgroups is as follows:

A time-frequency resource mapped by the DMRS port group 1 includes, infrequency domain, the 12n^(th), the (12n+1)^(th), the (12n+6)^(th), andthe (12n+7)^(th) subcarriers on a resource unit.

A time-frequency resource mapped by the DMRS port group 2 includes, infrequency domain, the (12n+2)^(th), the (12n+3)^(th), the (12n+8)^(th),and the (12n+9)^(th) subcarriers on a resource unit.

A time-frequency resource mapped by the DMRS port group 3 includes, infrequency domain, the (12n+4)^(th), the (12n+5)^(th), the (12n+10)^(th),and the (12n+11)^(th) subcarriers on a resource unit.

n may be any one or more integers greater than or equal to 0 and lessthan └M/12┘.

In the following descriptions, that a resource unit includes Msubcarriers in frequency domain is used as an example for description,where M is an integer greater than or equal to 1. For example, if theresource unit is one RB pair (in other words, two RBs in time domain),M=12; or if the resource unit is two RBs in frequency domain, M=24. EachCDM group occupies two consecutive symbols in time domain.

It is assumed that the DMRS port group 1 includes DMRS ports {1, 2, 7,8}, the DMRS port group 2 includes DMRS ports {3, 4, 9, 10}, and theDMRS port group 3 includes DMRS ports {5, 6, 11, 12}. This is only anexample herein, and a specific DMRS port mapping manner is not limited.It should be noted that, when the DMRS port mapping manner changes, ratematching information also changes. According to the method described inthis solution, a person in the related art can simply obtain a ratematching solution satisfying the foregoing rate matching designprinciple. During specific implementation, if the DMRS port mappingmanner changes, the rate matching information also changes. In thiscase, it indicates that a quantized value of a quantity of orthogonaltransmission layers in the rate matching information also changes.Therefore, a correspondence between the DMRS indication information andthe quantized value of the quantity of orthogonal transmission layersmay be indicated by using a piece of signaling.

A value of the DMRS indication information may be expressed in twomanners: One is a decimal system, and the other is a binary system.

When the value is 0 (in decimal system) or 00 (in binary system), aquantized value (shown as RMI in the figure) that is of a quantity oforthogonal transmission layers and that corresponds to the value is 4,and it indicates that the current quantized layer quantity is 4. Whenthe value is 1 or 01, it indicates that RMI=8. When the value is 2 or10, correspondingly, RMI=12. When the value is 3 or 11, it indicatesthat RMI is reserved (a reserved value). During specific implementation,the value may be null or in another state, for example, a transmissionstate that corresponds to the second and the third port groups (or thefirst and the third port groups) and in which a quantized layer quantityis 4. In this case, it is assumed that a base station performsscheduling in a sequence of port group numbers.

In this case, when the DMRS indication information is indicated inbinary system, two bits may be used for indication.

Table 4 shows an SU/MU MIMO DMRS configuration information tablesupporting a maximum of 12 orthogonal ports, where the table is similarto a DMRS DCI signaling table in LTE, and is applicable to onlytransparent MU-MIMO. A receive end obtains, by using the table,information such as a DMRS port and a quantity of orthogonaltransmission layers of the receive end. In addition, the receive end mayfurther learn, based on RMI indicated by the received DMRS indicationinformation (a specific value), of a current quantized quantity oforthogonal transmission layers, a combination of currently used portgroup states, a quantity of orthogonal transmission layers that are notcurrently used by or a port group state that is not currently used by areceive end, or a resource unit that needs to be muted, so as to learnof the resource that is not occupied by DMRS and that is in resourcesavailable for carrying a DMRS, thereby obtaining DMRS port informationof another matched terminal and completing rate matching.

When the value of the DMRS indication information received by UE 0 is 1(in decimal system) or 01 (in binary system), it indicates that thequantized value of the current quantity of orthogonal transmissionlayers is 8, thereby knowing that both the DMRS port group 1 and theDMRS port group 2 are occupied. The UE 0 obtains port information of theUE 0 with reference to Table 4, and knows that the DMRS port group 1includes a DMRS port of the UE 0 but the DMRS port group 2 does notinclude the DMRS port of the UE 0, so that the UE 0 learns that the DMRSport group 2 is used by another terminal, and does not transmit data ofthe UE 0. Likewise, the UE 1 learns, through indication, that thequantized value of the quantity of orthogonal transmission layers is 4,and obtains port information of the UE 1 with reference to Table 4, tolearn that the DMRS port group 1 and the DMRS port group 2 are occupied.So that the UE 1 learns that data of the UE 1 is not transmitted on alocation of the DMRS port group 1 that is not used by the UE 1. Inaddition, the UE 0 and the UE 1 learn, by using the rate matchinginformation, that data can be transmitted on a location of the DMRS portgroup 3.

The foregoing descriptions are merely examples. For different DMRSpatterns and different port mapping manners, values of the RMI andrepresentations of the DCI information tables may be different. Forexample, the RMI in the foregoing examples is a current quantized layerquantity, or may be a sequence number of a DMRS port group.

A system in FIG. 22 supports a maximum supported port quantity of 12. Inanother implementation, a TRP may further support another maximumsupported port quantity, for example, 4, 6, or 8. The maximum supportedport quantity supported by the TRP may be indicated by using explicitsignaling such as RRC, a MAC CE, or DCI, or may be bound with anotherconfiguration parameter, for example, a frequency, a carrier spacing, ora frame structure, corresponding to a scenario.

As shown in FIG. 24, a TRP 0 supports a maximum supported port quantityof 6, where ports allocated to a terminal 0 (the UE 0) are ports 1 and2, and ports allocated to a terminal 1 (the UE 1) are ports 3 and 4.

In this scenario, a DMRS port used by the UE 0 and the UE 1 ismultiplexed in a plurality of manners. FIG. 25 is a schematic diagram ofa mapping rule of six DMRS ports, where each shaded box indicates an REto which one DMRS port group is mapped, and n=0. The six DMRS ports aregrouped into three DMRS port groups: a DMRS port group 1, a DMRS portgroup 2, and a DMRS port group 3.

A time-frequency resource mapped by the DMRS port group 1 includes atleast one of the 12n^(th), the (12n+1)^(th), the (12n+6)^(th), the(12n+7)^(th) subcarriers on a resource unit.

A time-frequency resource mapped by the DMRS port group 2 includes atleast one of the (12n+2)^(th), the (12n+3)^(th), the (12n+8)^(th), andthe (12n+9)^(th) subcarriers on a resource unit.

A time-frequency resource mapped by the DMRS port group 3 includes atleast one of the (12n+4)^(th), the (12n+5)^(th), the (12n+10)^(th), andthe (12n+11)^(th) subcarriers on a resource unit.

n may be any one or more integers greater than or equal to 0 and lessthan └M/12┘. Three CDM groups occupy one symbol in time domain.

When the value is 0 (in decimal system) or 00 (in binary system), aquantized value (shown as RMI in the figure) that is of a quantity oforthogonal transmission layers and that corresponds to the value is 2,and it indicates that the current quantized layer quantity is 4. Whenthe value is 1 or 01, it indicates that RMI=8. When the value is 2 or10, correspondingly, RMI=6. When the value is 3 or 11, it indicates thatRMI is reserved (a reserved value).

In this case, when the DMRS indication information is indicated inbinary system, two bits may be used for indication.

Likewise, the receive end may further learn, based on RMI indicated bythe received DMRS indication information (a specific value of thevalue), of a current quantized quantity of orthogonal transmissionlayers, a combination of currently used port group states, a quantity oforthogonal transmission layers that are not currently used by or a portgroup state that is not currently used by a receive end, or a resourceunit that needs to be muted, so as to learn of the resource that is notoccupied by DMRS and that is in resources available for carrying a DMRS,thereby obtaining DMRS port information of another matched terminal andcompleting rate matching. Further, with reference to the SU/MU MIMO DMRSsignaling table supporting six orthogonal DMRS ports in Table 2, DMRSport information of another matched terminal may be obtained. Forexample, when the value of the DMRS indication information received bythe UE 0 is 1 (in decimal system) or 01 (in binary system), it indicatesthat the quantized value of the current quantity of orthogonaltransmission layers is 4. Assuming that the DMRS port group 1 includesDMRS ports {1, 2}, the DMRS port group 2 includes DMRS ports {3, 4}, andthe DMRS port group 3 includes DMRS ports {5, 6}, based on the ratematching information, it can be learned that the DMRS port group 1 andthe DMRS port group 2 are used and the DMRS port group 3 is not used. Inthis case, the terminal may learn of a port group location of anotherterminal with reference to the DMRS port information of the terminal.

As shown in FIG. 26, a TRP 0 supports a maximum supported port quantityof 8, where ports allocated to a terminal 0 (the UE 0) are ports 1, 2,3, and 4, and ports allocated to a terminal 1 (the UE 1) are ports 5, 6,7, and 8.

In this scenario, a DMRS port used by the UE 0 and the UE 1 may bemultiplexed in a plurality of manners. FIG. 27 is a schematic diagram ofa mapping rule of eight DMRS ports, where each shaded box indicates anRE to which one DMRS port group is mapped, and n=0. The eight DMRS portsare grouped into two DMRS port groups: a DMRS port group 1 and a DMRSport group 2, and each DMRS port group includes four DMRS ports.

A same time-frequency resource is multiplexed through CDM for DMRSscorresponding to the DMRS ports in each DMRS port group. A mapping ruleof the two DMRS port groups is as follows:

A time-frequency resource mapped by each DMRS port group is mapped totwo consecutive symbols in time domain.

A time-frequency resource mapped by the DMRS port group 1 includes atleast one of the 12n^(th), the (12n+2)^(th), the (12n+4)^(th), the(12n+6)^(th), the (12n+8)^(th), and the (12n+10)^(th) subcarriers on aresource unit.

A time-frequency resource mapped by the DMRS port group 2 includes atleast one of the (12n+1)^(th), the (12n+3)^(th), the (12n+5)^(th), the(12n+7)^(th), the (12n+9)^(th), and the (12n+11)^(th) subcarriers on aresource unit.

n may be any one or more integers greater than or equal to 0 and lessthan └M/12┘.

When the value is 0 (in decimal system) or 00 (in binary system), aquantized value (shown as RMI in the figure) that is of a quantity oforthogonal transmission layers and that corresponds to the value is 4,and it indicates that the current quantized layer quantity is 4. Whenthe value is 1 or 01, it indicates that RMI=8. In addition, the valuemay represent a combination of two CDM groups. For example, when thevalue is 0 (in decimal system) or 00 (in binary system), it indicatesthat the DMRS port group 1 is used. When the value is 1 or 01, both theDMRS port group 1 and the DMRS port group 2 are used.

In this case, when the DMRS indication information is indicated inbinary system, one bit may be used for indication.

Likewise, the receive end may further learn, based on RMI indicated bythe received DMRS indication information (a specific value of thevalue), of a current quantized quantity of orthogonal transmissionlayers, a combination of currently used port group states, a quantity oforthogonal transmission layers that are not currently used by or a portgroup state that is not currently used by a receive end, or a resourceunit that needs to be muted, so as to learn of the resource that is notoccupied by DMRS and that is in resources available for carrying a DMRS,thereby obtaining DMRS port information of another matched terminal andperforming rate matching. The following uses a port group statecombination as an example. For a solution of a quantized parameter layerquantity, refer to the foregoing examples. For example, when the valueof the DMRS indication information received by the UE 0 is 1 (in decimalsystem) or 01 (in binary system), it indicates that both the DMRS portgroup 1 and the DMRS port group 2 are occupied. The UE 0 learns, basedon the DMRS port information obtained by the UE 0, that a DMRS portgroup used by the UE 0, so that the UE 0 knows that the other port groupis used by another UE, and does not transmit data of the UE 0, therebyperforming rate matching.

As shown in FIG. 28, a TRP 0 supports a maximum supported port quantityof 4, where ports allocated to a terminal 0 (the UE 0) are ports 1 and2, and ports allocated to a terminal 1 (the UE 1) are ports 3 and 4. Inthis scenario, a DMRS port used by the UE 0 and the UE 1 may have aplurality of CDM multiplexing modes. FIG. 29 is a schematic diagram of amapping rule of four DMRS ports, where each shaded box indicates an REto which one DMRS port group is mapped, and n=0. Four DMRS ports aregrouped into two DMRS port groups: a DMRS port group 1 and a DMRS portgroup 2, and each DMRS port group includes two DMRS ports.

A same time-frequency resource is multiplexed through CDM for DMRSscorresponding to the DMRS ports in each DMRS port group. A mapping ruleof the two DMRS port groups is as follows:

A time-frequency resource mapped by each DMRS port group is mapped toone symbol in time domain.

A time-frequency resource mapped by the DMRS port group 1 includes the2n^(th) subcarrier on a resource unit.

A time-frequency resource mapped by the DMRS port group 2 includes the(2n+1)^(th) subcarrier on a resource unit.

n may be any one or more integers greater than or equal to 0 and lessthan └M/12┘.

It is assumed that the DMRS port group 1 includes DMRS port {1, 3}, andthe DMRS port group 2 includes DMRS port {2, 4}. In this case, when thevalue is 0 (in decimal system) or 00 (in binary system), a quantizedvalue (shown as RMI in the figure) that is of a quantity of orthogonaltransmission layers and that corresponds to the value is 2, and itindicates that the current quantized layer quantity is 4. When the valueis 1 or 01, it indicates that RMI=8.

In this case, when the DMRS indication information is indicated inbinary system, one bit may be used for indication.

Likewise, the receive end may further learn, based on RMI indicated bythe received DMRS indication information (a specific value of thevalue), of a current quantized quantity of orthogonal transmissionlayers, a combination of currently used port group states, a quantity oforthogonal transmission layers that are not currently used by or a portgroup state that is not currently used by a receive end, or a resourceunit that needs to be muted, so as to obtain DMRS port information ofanother matched terminal, thereby performing rate matching. For example,when the value of the indication information received by the UE 0 is 1(in decimal system) or 01 (in binary system), it indicates that thequantized value of the current quantity of orthogonal transmissionlayers is 4. In this case, the terminal learns, by using the ratematching information, that both the DMRS port group 1 and the DMRS portgroup 2 are occupied, and may learn, with reference to a DMRS port usedby the terminal, of a DMRS port group used by another terminal, therebyperforming rate matching. It should be noted that, in the solutions inFIG. 27 and FIG. 29, when the quantity of orthogonal transmission layerscan also be quantized into 1 and 2 based on a scheduling sequence of thebase station, for example, first FDM scheduling and then CDM scheduling,the rate matching information in this embodiment may correspond to aDMRS pattern configuration (type) or a quantity of port groups includedin a DMRS pattern, thereby reducing storage overheads of the receiveend.

When the TRP supports maximum supported port quantities 4, 6, 8, 12, andthe like, for different DMRS patterns and DMRS port mapping manners,maximum supported orthogonal-transmission-layer quantities may bedifferent. A conclusive rule is as follows:

The quantized quantity of orthogonal transmission layers may be obtainedin the following manner. A rule is provided only herein. During specificimplementation, a value may be directly stored without a selectionprocess.

It is assumed that all DMRS ports are quantized from 1. In this case, ineach DMRS port group, when port numbers are sorted in ascending order, aquantized layer quantity may be as follows:

for example, a port group 1 {1, 2, 3, 4} and a port group 2 {5, 6, 7, 8}are quantized into 4 and 8;

for example, a port group 1 {1, 3, 5, 7} and a port group 2 {2, 4, 6, 8}are quantized into 1 and 2;

for example, a port group 1 {1, 2, 5, 7} and a port group 2 {3, 4, 6, 8}are quantized into 2 and 4;

for example, a port group 1 {1, 2, 5, 6} and a port group 2 {3, 4, 6, 7}are quantized into 2 and 4;

for example, a port group 1 {1, 2, 3, 4}, a port group 2 {5, 6, 7, 8},and a port group 2 {9, 10, 11, 12} are quantized into 4, 8, and 12;

for example, a port group 1 {1, 4, 7, 10}, a port group 2 {2, 5, 8, 11},and a port group 2 {3, 6, 9, 12} are quantized into 1, 2 and 3;

for example, a port group 1 {1, 2, 7, 8}, a port group 2 {3, 4, 9, 10},and a port group 2 {5, 6, 11, 12} are quantized into 2, 4, and 6; and

for example, a port group 1 {1, 2, 7, 10}, a port group 2 {3, 4, 8, 11},and a port group 2 {5, 6, 9, 12} are quantized into 2, 4, and 6.

According to the foregoing embodiments, designing a corresponding DMRSconfiguration information table for each maximum supportedorthogonal-port quantity can satisfy requirements for differentscenarios in an NR system.

Embodiment 6

Different signaling is designed for different DMRS patterns forindication. For different DMRS port mapping manners, content in a tablemay be different, and may be a quantized currentorthogonal-transmission-layer quantity, or may be a status of a DMRSport group.

FIG. 30(a) to FIG. 30(e) show a DMRS pattern in which a mapping order isfirst CDM mapping and then FDM mapping.

For each DMRS pattern, overheads of corresponding indication informationare different. For example:

For a pattern that is shown in FIG. 30(a) and that supports fourorthogonal ports, one bit is required to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching information(RMI) is 2, in other words, a quantized value of a current quantity oforthogonal transmission layers is 2. When a value is 1 or 01, itindicates that rate matching information RMI is 4.

For a pattern that is shown in FIG. 30(b) and that supports eightorthogonal ports, one bit is required to indicate RM. When a value of anRM indication is 0 or 00, it indicates that rate matching RMI is 4. Whena value is 1 or 01, it indicates that rate matching RMI is 8.

For a pattern that is shown in FIG. 30(c) and that supports sixorthogonal ports, two bits are needed to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 2. When a value is 1 or 01, it indicates that rate matchingindication (RMI) is 4. When a value is 2 or 10, it indicates that ratematching indication (RMI) is 6.

For a pattern that is shown in FIG. 30(d) and that supports 12orthogonal ports, two bits are needed to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 4. When a value is 1 or 01, it indicates that rate matchingindication (RMI) is 8. When a value is 2 or 10, it indicates that ratematching indication (RMI) is 12.

For a pattern that is shown in FIG. 30(e) and that supports 12orthogonal ports, two bits are needed to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 2. When a value is 1 or 01, it indicates that rate matchingindication (RMI) is 4. When a value is 2 or 10, it indicates that ratematching indication (RMI) is 6.

FIG. 31(a) to FIG. 31(d) show a DMRS pattern in which a mapping order isfirst FDM mapping and then CDM mapping.

For each DMRS pattern, overheads of corresponding indication informationare different. For example:

For a pattern that is shown in FIG. 31(a) and that supports fourorthogonal ports, one bit is required to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 1. When a value is 1 or 01, it indicates that rate matchingindication (RMI) is 2.

For a pattern that is shown in FIG. 31(b) and that supports eightorthogonal ports, one bit is required to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 1. When a value is 1 or 01, it indicates that rate matchingindication (RMI) is 2.

For a pattern that is shown in FIG. 31(c) and that supports sixorthogonal ports, two bits are needed to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 1. When a value is 1 or 01, it indicates that rate matchingindication (RMI) is 2. When a value is 2 or 10, it indicates that ratematching indication (RMI) is 3. When a value of an RM indication is 3 or11, it indicates that rate matching indication (RMI) is reserved.

For a pattern that is shown in FIG. 31(d) and that supports 12orthogonal ports, two bits are needed to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 1. When a value is 1 or 01, it indicates that rate matching RMIis 2. When a value is 2 or 10, it indicates that rate matchingindication (RMI) is 3. When a value is 3 or 11, it indicates that ratematching indication (RMI) is reserved.

In addition, in this port mapping solution, a plurality of DMRS patternsmay correspond to a same RM table. For example, FIG. 31(a) and FIG.31(b) may correspond to a same rate matching table, for example, a tablein FIG. 31(a), and FIG. 31(c) and FIG. 31(d) may correspond to a samerate matching table, for example, a table in FIG. 31(c). In addition,the table may correspond to a DMRS type or a quantity of port groups ina DMRS pattern. The method has an advantage of reducing storageoverheads of a terminal.

FIG. 32(a) to FIG. 32(d) show a mapping order that is a hybrid CDM-FDMport mapping manner.

For each DMRS pattern, overheads of corresponding indication informationare different. For example:

For a pattern that is shown in FIG. 32(a) and that supports fourorthogonal ports, one bit is required to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 2. When a value is 1 or 01, it indicates that rate matchingindication (RMI) is 4.

For a pattern that is shown in FIG. 32(b) and that supports eightorthogonal ports, one bit is required to indicate information RMI. Whena value of an RM indication is 0 or 00, it indicates that rate matchingindication (RMI) is 2. When a value is 1 or 01, it indicates that ratematching indication (RMI) is 4.

For a pattern that is shown in FIG. 32(c) and that supports sixorthogonal ports, two bits are needed to indicate information RMI. Whena value of an RM indication is 0 or 00, it indicates that rate matchingindication (RMI) is 2. When a value is 1 or 01, it indicates that ratematching indication (RMI) is 4. When a value is 2 or 10, it indicatesthat rate matching indication (RMI) is 6. When a value is 3 or 11, itindicates that a value of rate matching indication (RMI) is reserved.

For a pattern that is shown in FIG. 32(d) and that supports 12orthogonal ports, two bits are needed to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 2. When a value is 1 or 01, it indicates that rate matching RMIis 4. When a value is 2 or 10, it indicates that rate matchingindication (RMI) is 6. When a value of an RM indication is 3 or 11, itindicates that rate matching indication (RMI) is reserved.

In addition, in this port mapping solution, a plurality of DMRS patternsmay correspond to a same RM table. For example, FIG. 32(a) and FIG.32(b) may correspond to a same rate matching table, for example, a tablein FIG. 32(a), and FIG. 32(c) and FIG. 32(d) may correspond to a samerate matching table, for example, a table in FIG. 32(c). In addition,the table may correspond to a DMRS type or a quantity of port groups ina DMRS pattern. The method has an advantage of reducing storageoverheads of the terminal.

FIG. 33(a) to FIG. 33(d) show a use status of a port group in a DMRSpattern.

For each DMRS pattern, overheads of corresponding DMRS indicationinformation are different. For example:

For a pattern that is shown in FIG. 33(a) and that supports fourorthogonal ports, one bit is required to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 1. In other words, a DMRS port group 1 is occupied. When avalue is 1 or 01, it indicates that rate matching indication (RMI) is 2.In this case, it indicates that both DMRS port groups 1 and 2 areoccupied.

For a pattern that is shown in FIG. 33(b) and that supports eightorthogonal ports, one bit is required to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 1. In other words, a DMRS port group 1 is occupied. When avalue is 1 or 01, it indicates that rate matching indication (RMI) is 2.In this case, it indicates that both DMRS port groups 1 and 2 areoccupied.

Optionally, FIG. 33(a) and FIG. 33(b) may correspond to a same ratematching table, for example, a table in FIG. 33(a). In this case, thetable may correspond to a DMRS type or a quantity of port groups in aDMRS pattern. The method has an advantage of reducing storage overheadsof a terminal.

For a pattern that is shown in FIG. 33(c) and that supports sixorthogonal ports, two bits are needed to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 1. In this case, it indicates that a DMRS port group 1 isoccupied. When a value is 1 or 01, it indicates that rate matchingindication (RMI) is 2. In this case, it indicates that both DMRS portgroups 1 and 2 are occupied. When a value is 2 or 10, it indicates thatrate matching indication (RMI) is 3. In this case, it indicates thatDMRS port groups 1, 2, and 3 are all occupied. When a value is 3 or 11,it indicates that rate matching indication (RMI) is 4. In this case, itindicates that both DMRS port groups 2 and 3 are occupied. It should benoted that, during specific implementation, RMI=4 may alternatively bepredefined as a state in which both DMRS port groups 1 and 3 areoccupied or reserved.

For a pattern that is shown in FIG. 33(d) and that supports 12orthogonal ports, two bits are needed to indicate RMI. When a value ofan RM indication is 0 or 00, it indicates that rate matching indication(RMI) is 1. In this case, it indicates that a DMRS port group 1 isoccupied. When a value is 1 or 01, it indicates that rate matchingindication (RMI) is 2. In this case, it indicates that both DMRS portgroups 1 and 2 are occupied. When a value is 2 or 10, it indicates thatrate matching indication (RMI) is 3. In this case, it indicates thatDMRS port groups 1, 2, and 3 are all occupied. When a value is 3 or 11,it indicates that rate matching indication (RMI) is 4. In this case, itindicates that both DMRS port groups 2 and 3 are occupied. It should benoted that, during specific implementation, RMI=4 may alternatively bepredefined as a state in which both DMRS port groups 1 and 3 areoccupied or reserved.

Optionally, FIG. 33(c) and FIG. 33(d) may correspond to a same ratematching table. In this case, the table may correspond to a DMRS type ora quantity of port groups in a DMRS pattern. The method has an advantageof reducing storage overheads of a terminal.

It should be noted that, a CDM combination in this solution is only anexample. During a specific implementation process, the CDM combinationmay be removed or added, or may be replaced with another DMRS statecombination.

It should be noted that, in an actual implementation process, the valuemay directly correspond to a state combination in which a port group isoccupied, without being indicated by using RMI. For example, for FIG.33(a), the state combination may be described as Table 19-1.

TABLE 19-1 Value Description 0/00 A DMRS port group 1 is occupied. 1/01A DMRS port group 1 and a DMRS port group 2 are occupied.

In addition, optionally, an SU state may be added to a table, forexample, Table 19-2.

TABLE 19-2 Value Description 0/00 SU or layer 0 being occupied . . . . ..

Herein, the layer 0 is mainly used to notify the terminal of a currentSU state, but a specific expression form is not limited.

According to the embodiments shown in FIG. 30 to FIG. 33, for eachpattern or a type of DMRS configuration (type) or DMRS patterns having asame quantity of port groups, corresponding DMRS indication informationmay be designed to satisfy requirements for different scenarios in an NRsystem. For example, the DMRS indication information is not only appliedto a pattern in an ultra-reliable and low latency communication (URLLC)scenario but also applied to a pattern in Enhanced Mobile Broadband(eMBB). For other different patterns, a design of a table isre-considered.

Embodiment 7

Ranked indication may be performed on the DMRS configuration informationand the DMRS indication information by using a combination of RRC, aMAC-CE, and DCI. For example, parameter setting may be configured byusing RRC, and include information about a quantized quantity oforthogonal transmission layers or CDM group state information for DMRSrate matching, and DCI signaling is used to select a parameter set tonotify a terminal. The foregoing plurality of methods for quantizing anorthogonal-transmission-layer quantity may be placed into the parameterset, where the parameter set may include other information, for example,a ZP-CSI-RS, a start location and an end location of a PDSCH, or thelike. Herein the table is only provided as an example, and a specifictable form, size, and description form are not limited. During specificimplementation, the parameter set may be configured by using RRC, wherethe parameter set may include rate matching information related to aDMRS, as shown in Table 20.

TABLE 20 Value Description 0/00 Parameter set 1 1/01 Parameter set 22/10 Parameter set 3 3/11 Parameter set 4 . . . . . .

Embodiment 8

In this embodiment, information related to a total quantity oforthogonal transmission layers or a total quantity of orthogonal ports(in this specification, the total quantity of orthogonal transmissionlayers and the total quantity of orthogonal ports are the same) isdesigned in a DMRS configuration information table. The informationrelated to the total quantity of orthogonal ports is reflected by usinga piece of indication information. The indication information mayindicate a quantity of all orthogonal ports that are possibly actuallypresented or a quantized value of a quantity of all orthogonal portsthat are possibly actually presented. The quantized value of thequantity of all the orthogonal ports may be information about a quantityof orthogonal DMRS layers, orthogonal DMRS antenna port set indicationinformation, orthogonal DMRS antenna port CDM group information, orinformation generated based on a CDM group size.

For four patterns in FIG. 34(a), FIG. 34(b), FIG. 34(c), and FIG. 34(d)of FIG. 34, compared with the DMRS configuration information tables inTable 1 to Table 4, in this embodiment, a feature of indicationinformation of the total quantity of orthogonal transmission layers isadded. For example, the column of total or total layer number ininformation tables shown in Table 21 to Table 24 is the indicationinformation of the total quantity of orthogonal transmission layers.

TABLE 21 Port combinations for 1-symbol pattern in config. 1 OneCodeword (≤4 layers): Two Codewords (>4 layers): Codeword 0 enabled,Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabled QuantizedPort Quantized Port Value layer num index Value layer num UE rank index0 2 1 0 0 reserved reserved reserved 1 2 1 1 1 reserved reservedreserved 2 2 2 0-1 2 reserved reserved reserved 3 4 1 0 3 reservedreserved reserved 4 4 1 1 4 reserved reserved reserved 5 4 1 2 5reserved reserved reserved 6 4 1 3 6 reserved reserved reserved 7 4 20-1 7 reserved reserved reserved 8 4 2 2-3 8 reserved reserved reserved9 4 3 0-2 9 reserved reserved reserved 10 4 4 0-3 10 reserved reservedreserved

TABLE 22 Port combinations for 2-symbol pattern in config. 1 OneCodeword (≤4 layers): Two Codewords (>4 layers): Codeword 0 enabled,Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabled QuantizedPort Quantized Port Value layer num index Value layer num UE rank index0 4 1 0 0 8 5 0-4 1 4 1 1 1 8 6 0-5 2 4 1 2 2 8 7 0-6 3 4 1 3 3 8 8 0-74 4 2 0-1 4 reserved reserved reserved 5 4 2 2-3 5 reserved reservedreserved 6 4 3 0-2 6 reserved reserved reserved 7 4 4 0-3 7 reservedreserved reserved 8 8 1 0 8 reserved reserved reserved 9 8 1 1 9reserved reserved reserved 10 8 1 2 10 reserved reserved reserved 11 8 13 11 reserved reserved reserved 12 8 1 4 12 reserved reserved reserved13 8 1 5 13 reserved reserved reserved 14 8 1 6 14 reserved reservedreserved 15 8 1 7 15 reserved reserved reserved 16 8 2 0-1 16 reservedreserved reserved 17 8 2 2-3 17 reserved reserved reserved 18 8 2 4-5 18reserved reserved reserved 19 8 2 6-7 19 reserved reserved reserved 20 83 0-2 20 reserved reserved reserved 21 8 3 3-5 21 reserved reservedreserved 22 8 4 0-3 22 reserved reserved reserved 23 8 4 4-7 23 reservedreserved reserved

TABLE 23 Port combinations for 1-symbol pattern in config. 2 OneCodeword (≤4 layers): Two Codewords (>4 layers): Codeword 0 enabled,Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabled QuantizedPort Quantized Port Value layer num index Value layer num UE rank index0 2 1 0 0 6 5 0-4 1 2 1 1 1 6 6 0-5 2 2 2 0-1 2 8 7 0-6 3 4 1 0 3 8 80-7 4 4 1 1 4 reserved reserved reserved 5 4 1 2 5 reserved reservedreserved 6 4 1 3 6 reserved reserved reserved 7 4 2 0-1 7 reservedreserved reserved 8 4 2 2-3 8 reserved reserved reserved 9 4 3 0-2 9reserved reserved reserved 10 4 4 0-3 10 reserved reserved reserved 11 61 0 11 reserved reserved reserved 12 6 1 1 12 reserved reserved reserved13 6 1 2 13 reserved reserved reserved 14 6 1 3 14 reserved reservedreserved 15 6 1 4 15 reserved reserved reserved 16 6 1 5 16 reservedreserved reserved 17 6 2 0-1 17 reserved reserved reserved 18 6 2 2-3 18reserved reserved reserved 19 6 2 4-5 19 reserved reserved reserved 20 63 0-2 20 reserved reserved reserved 21 6 3 3-5 21 reserved reservedreserved 22 6 4 0-3 22 reserved reserved reserved

TABLE 24 Port combinations for 2-symbol pattern in config. 2 OneCodeword (≤4 layers): Two Codewords (>4 layers): Codeword 0 enabled,Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabled QuantizedPort Quantized Port Value layer num index Value layer num UE rank index0 4 1 0 0 8 5 0-4 1 4 1 1 1 8 6 0-5 2 4 1 2 2 8 7 0-6 3 4 1 3 3 8 8 0-74 4 2 0-1 4 reserved reserved reserved 5 4 2 2-3 5 reserved reservedreserved 6 4 3 0-2 6 reserved reserved reserved 7 4 4 0-3 7 reservedreserved reserved 8 8 1 0 8 reserved reserved reserved 9 8 1 1 9reserved reserved reserved 10 8 1 2 10 reserved reserved reserved 11 8 13 11 reserved reserved reserved 12 8 1 4 12 reserved reserved reserved13 8 1 5 13 reserved reserved reserved 14 8 1 6 14 reserved reservedreserved 15 8 1 7 15 reserved reserved reserved 16 8 2 0-1 16 reservedreserved reserved 17 8 2 2-3 17 reserved reserved reserved 18 8 2 4-5 18reserved reserved reserved 19 8 2 6-7 19 reserved reserved reserved 20 83 0-2 20 reserved reserved reserved 21 8 3 3-5 21 reserved reservedreserved 22 8 4 0-3 22 reserved reserved reserved 23 8 4 4-7 23 reservedreserved reserved 28 12 1 0 28 reserved reserved reserved 29 12 1 1 29reserved reserved reserved 30 12 1 2 30 reserved reserved reserved 31 121 3 31 reserved reserved reserved 32 12 1 4 32 reserved reservedreserved 33 12 1 5 33 reserved reserved reserved 34 12 1 6 34 reservedreserved reserved 35 12 1 7 35 reserved reserved reserved 36 12 1 8 36reserved reserved reserved 37 12 1 9 37 reserved reserved reserved 38 121 10  38 reserved reserved reserved 39 12 1 11  39 reserved reservedreserved 40 12 2 0-1 40 reserved reserved reserved 41 12 2 2-3 41reserved reserved reserved 42 12 2 4-5 42 reserved reserved reserved 4312 2 6-7 43 reserved reserved reserved 44 12 2 8-9 44 reserved reservedreserved 45 12 2 10-11 45 reserved reserved reserved 46 12 3 0-2 46reserved reserved reserved 47 12 3 3-5 47 reserved reserved reserved 4812 3 6-8 48 reserved reserved reserved 49 12 3  9-11 49 reservedreserved reserved 50 12 4 0-3 50 reserved reserved reserved 51 12 4 4-751 reserved reserved reserved 52 12 4  8-11 52 reserved reservedreserved

In this embodiment, all total quantities of orthogonal transmissionlayers that are possibly presented are considered, and this embodimentmay be adapted to all scenarios, and may be used by a plurality ofterminals for MU matching to perform rate matching.

Based on the content of the DMRS configuration information tablesprovided in the foregoing embodiment, in this embodiment, the feature ofthe total quantity of orthogonal transmission layers, in other words,information about a quantized layer quantity, is added. A terminal mayimplicitly obtain RMI information with reference to the information.

In this embodiment, all total quantities of orthogonal transmissionlayers that are possibly presented are considered, and this embodimentmay be adapted to all scenarios. The quantized layer num is a quantizedvalue of a possible quantity of orthogonal transmission layers, and isindicated by using a value the same as that of DMRS indicationinformation (a value) in a DMRS configuration information table. TheDMRS configuration information table may be similar to that in LTE. Forexample, the DMRS indication information is a quantity of antenna ports,a scrambling identification, and an indication of a quantity oforthogonal transmission layers (number of layers indication) that are inLTE. The DMRS configuration information table may further include atleast one of a DMRS port quantity, a port index, sequence generationinformation, and a CDM type. Based on this, the quantized value of thequantity of orthogonal transmission layers is added. The DMRSconfiguration information table may be stored at both a transmit end anda receive end. When the transmit end needs to indicate a rate matchingsolution to the receive end, the transmit end needs to send only a pieceof indication information to the receive end. After receiving theindication information, the receive end uses the indication informationas an index, to search the DMRS configuration information table for thequantized value of the corresponding quantity of orthogonal transmissionlayers, and also learn of information about a quantity of DMRS layers,information about a DMRS antenna port set, code division multiplexingCDM group information of a DMRS antenna port, or the like. Then, thereceive end identifies which resource units are used for DMRStransmission at the receive end and which resource units are used forDMRS transmission at other receive ends that implement CDM multiplexing.Remaining resource units are used for data transmission related to thereceive end. Therefore, the receive end demodulates data on acorresponding resource unit.

In another implementation, the indication information in this embodimentof this application indicates a state of a DMRS port group that is notused by the receive end. Specifically, DCI may be used for indication.

For configurations shown in FIG. 34(a) and FIG. 34(b), indication isperformed by using the following Table 25:

TABLE 25 Value MU Description 0 Non-mute 1 MU All-mute

Table 25 may be configured at the transmit end and the receive endaccording to a protocol, or may be sent by the transmit end to thereceive end by using RRC signaling.

Different from the foregoing embodiment, in Table 25, a value does notcorrespond to a quantized value of a quantity of orthogonal transmissionlayers, but indicates a status of a DMRS port group that is not used bythe receive end. For example, when the value is 0, regardless of SU orMU matching, it indicates that the state of the DMRS port group that isnot used by the receive end is non-mute. When the value is 1, itindicates that the state of the DMRS port group that is not used by thereceive end is all-mute. After receiving the indication information (thevalue), the receive end can determine the state of the DMRS port groupthat is not used by the receive end, thereby completing rate matching.It should be noted that the column of MU in Table 25 is only an example,and may be omitted during specific implementation.

For configurations shown in FIG. 34(c) and FIG. 34(d), in animplementation, whether a status of a DMRS port group that is not usedby the receive end is indicated, as shown in the following Table 26,where a larger set and a smaller set may be determined based on arelative relationship between port groups that are not used by thereceive end. For example, in a scenario of three port groups, when aterminal uses one port group, a larger port group and a smaller portgroup may be determined based on a relative relationship between (valuesof) maximum (or smallest) port numbers in the remaining two port groups.During specific implementation, a comparison process may not beincluded, and the larger and smaller port groups are directly prestored.

TABLE 26 Value SU/MU Description 0 SU Non-mute 1 MU Mute smaller set 2MU Mute larger set 3 MU All-mute

In another implementation, specific DMRS port groups that are not usedby the receive end are indicated. For example, when the receive end usesa port group 1, it indicates that the port group 1 is not muted when thevalue is 0, it indicates that another receive end performing MU matchinguses a port group 2 when the value is 1, it indicates that anotherreceive end performing MU matching uses a port group 3 when the value is2, and it indicates that another receive end performing MU matching usesa port group 2 and a port group 3 when the value is 3 During specificimplementation, a sequence number of a port group may not be defined. Aport number in a port group is used to indicate the port group. Forexample, the port group 2 includes ports {5, 6, 7, 8}. In this case, theport group 2 may be directly replaced with {5, 6, 7, 8} in the table,specifically as shown in Table 27.

TABLE 27 Value SU/MU Description 0 SU Non-mute 1 MU Port group 2 2 MUPort group 3 3 MU All port groups, or port group 2 and port group 3

In still another implementation, a multi-level indication of RRC+DCI isused as follows:

The DMRS rate matching information may be indicated by using amulti-level indication of RRC+DCI or a multi-level indication of RRC+MACCE+DCI.

With a plurality of parameter sets including the DMRS rate matchinginformation may be configured in RRC signaling, where the DMRS ratematching information is dynamically selected by using DCI signaling.

For example, two parameter sets are configured in the RRC signaling, and1-bit DCI signaling is used for dynamic selection. Alternatively, fourparameter sets are configured in the RRC signaling, and 2-bit DCIsignaling is used for dynamic selection. Details are shown in Table 28-1and Table 28-2.

TABLE 28-1 One bit case Value of ‘RE mapping’ field Description 0/‘00’Parameter set 1 configured by higher layers 1/‘01’ Parameter set 2configured by higher layers

TABLE 28-2 Two bits case Value of ‘RE mapping’ field Description 0/‘00’Parameter set 1 configured by higher layers 1/‘01’ Parameter set 2configured by higher layers 3/‘10’ Parameter set 3 configured by higherlayers 4/‘11’ Parameter set 4 configured by higher layers

The parameter set includes the DMRS rate matching information, and therate matching information may be expressed in a plurality of forms. Forexample:

The rate matching information may be four states provided in theforegoing solution, and specifically, four states corresponding tovalues 0, 1, 2, and 3.

The rate matching information may be state information indicatingwhether each CDM group is occupied. For example, CDM groups may benumbered as, for example, a DMRS CDM group 1, a DMRS CDM group 2, and aDMRS CDM group 3. During specific implementation, a state in which a CDMgroup is numbered may not exist, and a number of a corresponding DMRSCDM port group may be indicated by indicating a port number in a CDMgroup.

The rate matching information may be a specific location of a ZP DMRS,which corresponds to locations of a plurality of CDM groups (forexample, a bitmap is used, where two bits for config. 1, and three bitsfor config. 2).

The rate matching information may be a rate matching pattern, directlyindicating which REs on a DMRS symbol need to be muted. In this case,there is no concept of a CDM group.

In another implementation, in the DMRS configuration information table,the CDM group information is used to implement DMRS rate matching.

In an implementation, the RMI may be represented as the CDM group stateinformation, for example, the column of “State of CDM group” in Table8-1 and Table 8-2. The following provides descriptions by using anexample of a specific DMRS pattern, where a port number of the specificDMRS port is only used as an example. For different port mapping orders,a DMRS port number (port index) in the following embodiment may change.This is not limited herein.

With reference to FIG. 34 (a port group in FIG. 34 is a CDM port group),for an FL DMRS configuration type 1 corresponding to Table 8-1, a state1 (State of CDM group=1) represents that a CDM port group 1 (a part withoblique lines in FIG. 34(a) and FIG. 34(b)) is occupied, and a state 2represents that CDM groups 1 and 2 (a part with oblique lines and a partwith horizontal lines in FIG. 34(a) and FIG. 34(b)) are occupied.

For a DMRS type 2 corresponding to Table 8-2, a state 1 corresponds tothat a CDM group 1 (a part with oblique lines in FIG. 34(c) and FIG.34(d)) is occupied, a state 2 represents that CDM groups 1 and 2 (a partwith oblique lines and a part with horizontal lines in FIG. 34(c) andFIG. 34(d)) are occupied, and a state 3 represents that CDM groups 1, 2,and 3 (a part with oblique lines, a part with horizontal lines, and apart with vertical lines in FIG. 34(c) and FIG. 34(d)) are occupied.

The foregoing provides only an example of a CDM group occupation state.During specific implementation, each state may be replaced with anotherCDM group occupation state. In addition, during specific implementation,a CDM group state (for example, State of CDM group=1, 2, and 3 in thetables) specifically indicated in Table 8-1 and Table 8-2 may bereplaced with a number of an occupied CDM group (for example, a CDMgroup 1), or may be directly represented as all port numbers in a CDMgroup (for example, a CDM group 1 may be represented as port numbers 0and 1 or 0, 1, 4, and 6) or at least one DMRS port number in an occupiedCDM group (for example, a CDM group 1 may be represented as a portnumber 0 or port numbers 0 and 1). In addition, when the CDM group stateis represented as all port numbers in a CDM group, the column of numberof symbols may be omitted in Table 8-1 and Table 8-2, and a 1-symbol or2-symbol FL DMRS pattern may be implicitly indicated by directlyindicating all the port numbers in the CDM group. For example, for a1-symbol type 1, the CDM group 1 is represented as 0 and 1, and for a2-symbol type 1, the CDM group 1 is represented as 0, 1, 4, and 6. Thereceive end may implicitly obtain information about the 1-symbol DMRS orthe 2-symbol DMRS based on the port numbers in the CDM group.

In another implementation, RMI information in the table may indicate aquantity of occupied CDM groups. In other words, the “State of CDMgroup” in Table 8-1 and Table 8-2 may be replaced with “number of CDMgroups” or “number of co-scheduled CDM groups”. Specific literalexpression is not limited.

Table 29-1 provides an addition method corresponding to the DMRS type 1,where “number of co-scheduled CDM groups” indicates that one or two CDMgroups in type 1 are occupied. In an implementation method, the numberof CDM groups may be implemented based on a specific scheduling order,for example, obtained based on the current quantized quantity oforthogonal ports in the foregoing embodiment. In an implementationmethod, information about the number of CDM groups may directlycorrespond to a particular CDM group sequence number, or may be based ona specific scheduling rule. For example, for the DMRS type 1, one CDMgroup may correspond to that a CDM group 1 is occupied, and two CDMgroups may be understood as that a CDM group 1 and a CDM group 2 areoccupied. For the DMRS type 2, one CDM group may correspond to that aCDM group 1 is occupied, two CDM groups may be understood as that a CDMgroup 1 and a CDM group 2 are occupied, and three CDM groups may beunderstood as that CDM groups 1, 2, and 3 are occupied. In anotherimplementation method, the number of CDM groups may not be bound with aCDM group sequence number. For example, for the DMRS type 1, one CDMgroup indicates that only one CDM group is used in the system, and theCDM group may be a CDM group 1 or a CDM group 2. The receive end mayobtain a sequence number of the occupied CDM group based on a specificDMRS port number of the receive end. Two CDM groups indicate that thetwo CDM groups are both occupied. The receive end may use one or two ofthe CDM groups. If the receive end uses the CDM group 2, it can bededuced that the CDM group 1 is occupied by another receive end, therebyperforming rate matching.

TABLE 29-1 Example of a DMRS port combination type 1 One Codeword (≤4layers): Two Codewords (>4 layers): Codeword 0 enabled, Codeword 0enabled, Codeword 1 disabled Codeword 1 enabled Number of Number ofco-scheduled UE number of co-scheduled number of Value CDM groups rankPorts symbols Value CDM groups UE rank Ports symbols 0 1 1 0 1 0reserved reserved reserved 1 1 1 1 1 1 1 reserved reserved reserved 1 21 2 0-1 1 2 reserved reserved reserved 1 3 2 1 0 1 3 reserved reservedreserved 1 4 2 1 1 1 4 reserved reserved reserved 1 5 2 1 2 1 5 reservedreserved reserved 1 6 2 1 3 1 6 reserved reserved reserved 1 7 2 2 0-1 17 reserved reserved reserved 1 8 2 2 2-3 1 8 reserved reserved reserved1 9 2 3 0-2 1 9 reserved reserved reserved 1 10 2 4 0-3 1 10 reservedreserved reserved 1 11 1 1 0 2 11 2 5 0-4 2 12 1 1 1 2 12 2 6 0-5 2 13 11 4 2 13 2 7 0-6 2 14 1 1 6 2 14 2 8 0-7 2 15 1 2 0-1 2 15 reservedreserved reserved 2 16 1 2 4, 6 2 16 reserved reserved reserved 2 17 1 30-1, 4 2 17 reserved reserved reserved 2 18 1 4 0-1, 4, 6 2 18 reservedreserved reserved 2 19 2 1 0 2 19 reserved reserved reserved 2 20 2 1 12 20 reserved reserved reserved 2 21 2 1 2 2 21 reserved reservedreserved 2 22 2 1 3 2 22 reserved reserved reserved 2 23 2 1 4 2 23reserved reserved reserved 2 24 2 1 5 2 24 reserved reserved reserved 225 2 1 6 2 25 reserved reserved reserved 2 26 2 1 7 2 26 reservedreserved reserved 2 27 2 2 0-1 2 27 reserved reserved reserved 2 28 2 22-3 2 28 reserved reserved reserved 2 29 2 2 4, 6 2 29 reserved reservedreserved 2 30 2 2 5, 7 2 30 reserved reserved reserved 2 31 2 3 0-1, 4 231 reserved reserved reserved 2 32 2 3 2-3, 5 2 32 reserved reservedreserved 2 33 2 4 0-1, 4, 6 2 33 reserved reserved reserved 2 34 2 42-3, 5, 7 2 34 reserved reserved reserved 2

In addition, in another implementation, a number of CDM groups added tothe table may not include a number of CDM groups used by the receiveend, in other words, a number of CDM groups that is indicated in thetable and currently used in the system and that does not include anumber of CDM groups used by the receive end, or may be understood as (atotal number of CDM groups occupied in the system—a number of CDM groupsused by the receive end). For example, for the type 1, when the systemhas a total of two CDM groups scheduled, and the receive end uses twoCDM groups, a number of CDM groups that are not used by the receive endis 0. When the system has a total of two CDM groups scheduled, and thereceive end uses one CDM group, a number of CDM groups that are not usedby the receive end is 1. When the system has only one CDM groupscheduled, and the receive end uses one CDM group, a number of CDMgroups that are not used by the receive end is 0. In this solution, thenumber of CDM groups may be replaced with the number of co-scheduled CDMgroups in Table D-1. For a specific table, a person skilled in the artmay directly derive the table based on the foregoing principle.

In addition, power boosting information may be further added to theforegoing DMRS configuration information table. For example, a column isadded to Table 29-1 to provide a specific power boosting value for eachstate. The specific values may be 0 dB and 3 dB for the type 1, and maybe 0 dB, 1.77 dB, and 4.77 dB for the type 2. In the table, the specificpower boosting value may be directly obtained, through deduction, basedon a number of CDM groups occupied for a current state and portinformation of the receive end, where the power boosting value may havea one-to-one correspondence with the state.

A specific principle is that, for the DMRS type 1, when the receive enduses one CDM port group, and the system currently has only one CDM portgroup occupied, a power boosting value is 0 dB. When the receive enduses two CDM port groups, and the system currently has two CDM portgroups occupied, a power boosting value is 0 dB. When the receive enduses one CDM port group, and the system currently has two CDM portgroups occupied, a power boosting value is 3 dB. Table 29-2 provides anexample of a corresponding DMRS type 1, and specific port scheduling anda specific number of symbols are not limited.

TABLE 29-2 Example of a DMRS port combination type 1 One Codeword (≤4layers): Codeword 0 enabled, Codeword 1 disabled Two Number of Powercode- co-scheduled UE number of boosting words Value CDM groups rankPorts symbols value . . . X1 1 1 0 1 or 2 0 dB . . . X2 2 1 0 1 or 2 3dB . . . X3 2 3 0, 1, 2 1 or 2 0 dB . . .

For the DMRS type 2, when the receive end uses one CDM port group, andthe system currently has only one CDM port group occupied, a powerboosting value is 0 dB. When the receive end uses two CDM port groups,and the system currently has two CDM port groups occupied, a powerboosting value is 0 dB. When the receive end uses one CDM port group,and the system currently has two CDM port groups occupied, a powerboosting value is 1.77 dB. When the receive end uses one CDM port group,and the system currently has three CDM port groups occupied, a powerboosting value is 4.77 dB. Herein, in a case of an MU, one receive endis limited to invoke only a maximum of four ports in one CDM group. Inother words, in the case of the MU, one receive end can occupy only amaximum of one CDM group. Table 29-3 provides an example of acorresponding DMRS type 2, and specific port scheduling and a specificnumber of symbols are not limited.

TABLE 29-3 Example of a DMRS port combination type 2 One Codeword (≤4layers): Codeword 0 enabled, Codeword 1 disabled Two Number of Powercode- co-scheduled UE number of boosting words Value CDM groups rankPorts symbols value . . . X1 1 1 0 1 or 2 0 dB . . . X2 2 4 0, 1, 2, 3 1or 2 0 dB . . . X3 2 2 0, 1 1 or 2 1.77 dB . . . X4 3 2 0, 1 1 or 2 4.77dB . . .

Embodiment 9

This embodiment is used to resolve a DMRS rate matching problem in anon-coherent joint transmission (NC-JT 2 PDCCH) scenario.

As shown in FIG. 35, in such a multi-TRP, NC-JT, and 2-PDCCH scenario,12 ports are supported, where a TRP 0 uses {1, 2, 7, 10}, and a TRP 1uses {3, 4, 5, 6, 8, 9, 11, 12}.

This embodiment provides a solution that is a protocol-default solution:A TRP defaults that an RE location corresponding to a DMRS that is inone or more QCL groups and that is not used by the TRP is muted. Forexample, for a DMRS pattern shown in FIG. 36, to be specific, two DMRSport groups, two TRPs each mute a time-frequency resource locationcorresponding to a DMRS port group that is not used by the TRP.Therefore, this solution can directly resolve the problem without extrasignaling indication.

Another solution is an independent indication solution, as shown in FIG.37. A TRP mutes, by default, an RE location corresponding to a DMRS thatis in one or more QCL groups and that is not used by the TRP. Inaddition, for a TRP having a plurality of port groups, the TRP sends anRM signaling to UE, where the rate matching signaling may be applicablebased on the solution that is previously described. It should be notedthat, in this case, the rate matching signaling is generated based on aDMRS port available for the current TRP, a maximum supported layerquantity, or a DMRS pattern corresponding to a DMRS port available forthe TRP. The UE completes rate matching based on the rate matchingsignaling previously received by the UE. The solution may be thesolution used in the foregoing embodiment. Herein, only one DMRS patternis used as an example. For different DMRS patterns, corresponding RMsignaling may be used.

For example, in FIG. 37, a TRP 0 can use only a DMRS port group 1, and aTRP 1 may use DMRS port groups 2 and 3. In this case, the TRP 0 mutestime-frequency resources corresponding to the DMRS port groups 2 and 3,and the TRP 1 mutes a time-frequency resource corresponding to the DMRSport group 1. In addition, a terminal receives rate matching signalingfrom the TRP 1, where the signaling indicates a total quantized quantityof orthogonal transmission layers of the port groups 2 and 3, in otherwords, a quantized quantity of orthogonal transmission layers of DMRSports available for the TRP 1. In this case, the TRP 0 may not have ratematching signaling, or rate matching signaling may be used to send astate representing an SU. The terminal receives the rate matchingsignaling of the TRP 1, completes rate matching, and demodulates datasent by the TRP 1.

It should be noted that in this embodiment, the indication informationmay also be used to indicate a DMRS port group that is not used by areceive end. For example, when the TRP 0 enters an NC-JT mode, nosignaling is required for indication, or original signaling is used forindication. For the TRP 1, the following table is used for indication.When a value is 0, it indicates that a DMRS port group that is not usedby the TRP 1 is muted. When a value is 1, DMRS port groups that are notused by the TRP 1 are all muted. Details are shown in Table 30.

TABLE 30 Value Description 0 non-mute 1 all-mute

Embodiment 10

Embodiment 10 is applicable to a dynamic TDD scenario or a flexibleduplex scenario.

As shown in FIG. 38, in the dynamic TDD scenario, 12 ports aresupported, where a TRP 0 uses DMRS ports {1, 2, 3, 4} and a TRP 1 usesDMRS ports {5, 6, 7, 8}.

This embodiment provides a solution that is a protocol-default solution:A TRP defaults that an RE location corresponding to a DMRS that is inone or more QCL groups and that is not used by the TRP is muted. Forexample, for a DMRS pattern, to be specific, two DMRS port groups, shownin FIG. 39, a TRP 0 and a TRP 1 each use one DMRS port group, and mute atime-frequency resource location corresponding to a DMRS port group thatis not used by the TRP. Therefore, this solution can directly resolvethe problem without extra signaling indication.

Another solution is an independent indication solution, as shown in FIG.40. A TRP mutes, by default, an RE location corresponding to a DMRS thatis in one or more QCL groups and that is not used by the TRP. Inaddition, for a TRP having a plurality of port groups, the TRP sends anRM signaling to UE, where the rate matching signaling may be applicablebased on the solution that is previously described. It should be notedthat, in this case, the rate matching signaling may be generated basedon a DMRS port available for the current TRP or a DMRS patterncorresponding to an available DMRS port. The UE completes rate matchingbased on the rate matching signaling previously received by the UE. Thesolution may be the solution used in the foregoing embodiment. Herein,only one DMRS pattern is used as an example. For different DMRSpatterns, corresponding RM signaling may be used.

For example, in FIG. 40, a TRP 0 can use only a DMRS port group 1, and aTRP 1 may use DMRS port groups 2 and 3. In this case, the TRP 0 muteslocations corresponding to the DMRS port groups 2 and 3, and the TRP 1mutes a location corresponding to the DMRS port group 1. In addition, aterminal receives rate matching signaling from the TRP 1, where thesignaling indicates a quantized quantity of orthogonal transmissionlayers of the DMRS port groups 2 and 3, in other words, a quantizedquantity of orthogonal transmission layers of the TRP 1. In this case,the TRP 0 may not have rate matching signaling, or rate matchingsignaling may be used to send a state representing an SU. The terminalreceives the rate matching signaling of the TRP 1, completes ratematching, and demodulates data sent by the TRP 1.

It should be noted that in this embodiment, the indication informationmay also be used to indicate a DMRS port group that is not used by areceive end. For example, when the TRP 0 enters an NC-JT mode, nosignaling is required for indication, or original signaling is used forindication. For the TRP 1, the following table is used for indication.When a value is 0, it indicates that a DMRS port group that is not usedby the TRP 1 is muted. When a value is 1, DMRS port groups that are notused by the TRP 1 are all muted. Details are shown in Table 31.

TABLE 31 Value Description 0 non-mute 1 all-mute

The foregoing describes the solutions provided in the embodiments ofthis application mainly from the perspective of interaction betweennetwork elements. It may be understood that to implement the foregoingfunctions, the foregoing various network elements such as the basestation or the terminal include hardware structures and/or softwaremodules corresponding to the various functions. A person of ordinaryskill in the art should be easily aware that units and algorithm stepsin the examples described with reference to the embodiments disclosed inthis specification can be implemented by hardware or a combination ofhardware and computer software in this application. Whether a functionis performed by hardware or hardware driven by computer software dependson particular applications and design constraints of the technicalsolutions. A person skilled in the art may use different methods toimplement the described functions for each particular application, butit should not be considered that the implementation goes beyond thescope of this application.

In the embodiments of this application, functional module division maybe performed on the base station or the terminal according to theexamples of the methods. For example, various functional modules may bedivided based on the corresponding functions, or two or more functionsmay be integrated into one processing module. The integrated module maybe implemented in a form of hardware, or may be implemented in a form ofa software functional module. It should be noted that, in thisembodiment of this application, module division is an example, and ismerely a logical function division. During actual implementation,another division manner may be used. The following descriptions are madeby using an example in which function modules are divided correspondingto functions.

FIG. 41 is a schematic structural diagram of a transmit end 350. Thetransmit end 350 may be the base station 100 or the terminal 200 in theforegoing descriptions. The transmit end 350 may include a processingunit 3501 and a sending unit 3502. The processing unit 3501 may beconfigured to: perform S101 in FIG. 6, to be specific, selecting DMRSconfiguration information from a plurality of groups of DMRSconfiguration information tables, and obtaining DMRS indicationinformation based on the DMRS configuration information; or perform S201in FIG. 21, to be specific, generating demodulation reference signalDMRS indication information, where the DMRS indication informationcorresponds to a maximum supported port quantity, a DMRS pattern, or aDMRS configuration type; and/or configured to support another process inthe technology described in this specification. The sending unit 3502may be configured to perform S102 in FIG. 6 or S202 in FIG. 21 ofsending, by the transmit end, DMRS related information or the DMRSindication information on a time-frequency resource; and/or configuredto support another process in the technology described in thisspecification. All related content of the steps in the foregoing methodembodiments may be referred for the functional descriptions of thecorresponding functional modules. Details are not described hereinagain.

FIG. 42 is a schematic structural diagram of a receive end 360. Thereceive end 360 may include a processing unit 3602 and a receiving unit3603. The receive end 360 may be the terminal 200 or the base station100 in the foregoing descriptions. The receiving unit 3603 is configuredto: perform S103 in FIG. 6 of receiving, by the receive end, the DMRSindication information, or perform S203 in FIG. 21 of receiving, by thereceive end, the DMRS indication information; and/or perform an actionof receiving any information by the receive end in the embodiments ofthis application. The processing unit 3602 may be configured to: performS104 in FIG. 6, to be specific, performing channel estimation orassisting data demodulation based on the received DMRS indicationinformation, or perform S204 in FIG. 21, to be specific, obtaining ratematching information based on the DMRS indication information, anddemodulating data on a resource on which no DMRS is transmitted based onthe DMRS indication information, and demodulating data on a resource onwhich no DMRS is transmitted; and/or configured to support anotherprocess in the technology described in this specification. All relatedcontent of the steps in the foregoing method embodiments may be referredfor the functional descriptions of the corresponding functional modules.Details are not described herein again. For example, in a specificimplementation process, it may be understood as that the receive end 360first obtains a symbol carried on each RE (for example, obtains a symbolcarried on each OFDM symbol and each subcarrier), for example, but notlimited to, through inverse fast Fourier transform (IFFT), and thenobtains a DMRS from the obtained symbol based on a time-frequencyresource on which the DMRS is located.

In this embodiment of this application, the transmit end 350 and thereceive end 360 are presented in forms of functional modules dividedbased on functions, or presented in forms of functional modules dividedthrough integration. Herein, the “module” may refer to anapplication-specific integrated circuit (ASIC), a processor and a memoryexecuting one or more software or firmware programs, an integrated logiccircuit, and/or another component that can provide the foregoingfunctions, where the processor and the memory may be integrated togetheror may exist independently.

In a simple embodiment, a person skilled in the art may be aware thateither the transmit end 350 or the receive end 360 is implemented in astructure shown in FIG. 43.

As shown in FIG. 43, an apparatus 390 may include a memory 3902, aprocessor 3901, and a communications interface 3903. The memory 3902 isconfigured to store a computer executable instruction. When theapparatus 390 runs, the processor 3901 executes the computer executableinstruction stored in the memory 3902, so that the apparatus 390performs the DMRS indication method and the DMRS receiving methodprovided in the embodiments of this application. For the DMRS indicationmethod and the DMRS receiving method, refer to the foregoingdescriptions and related descriptions in the accompanying drawings, anddetails are not described herein again. The communications interface3903 may be a transceiver.

Optionally, the apparatus 390 may be a field-programmable gate array(field-programmable gate array, FPGA), an application-specificintegrated circuit (application-specific integrated circuit, ASIC), asystem on chip (SoC), a central processor unit (CPU), a networkprocessor (NP), a digital signal processor (DSP), or a micro controllerunit (MCU), or a programmable logic device (PLD) or another integratedchip may be used.

An embodiment of this application further provides a storage medium. Thestorage medium may include the memory 3902.

According to a first aspect of the embodiments of the present invention,a data sending method is provided. The method is used for sending aplurality of data streams to a receive-end device through a plurality ofdemodulation reference signal DMRS ports, where the plurality of DMRSports belong to at least two port groups, DMRS ports in each port groupsatisfy a quasi co-location QCL relationship, and any DMRS port in eachport group and any DMRS port in any other port group satisfy a non-quasico-location Non-QCL relationship. The plurality of DMRS ports areallocated to at least two transmit-end devices, and DMRS ports allocatedto each transmit-end device belong to a same port group. The methodincludes the following designs.

In a possible design, each transmit-end device maps a codeword to a datastream corresponding to a DMRS port allocated to the transmit-enddevice; and each transmit-end device sends, to the receive-end device,the data stream corresponding to the DMRS port allocated to thetransmit-end device.

In a possible design, the at least two transmit-end devices are at leasttwo antenna panels of a same transmit-end device; the mapping, by eachtransmit-end device, a codeword to a data stream corresponding to a DMRSport allocated to the transmit-end device is specifically: mapping, bythe same transmit-end device for each antenna panel, a codeword to adata stream corresponding to a DMRS port allocated to the antenna panel;and the sending, by each transmit-end device to the receive-end device,the data stream corresponding to the DMRS port allocated to thetransmit-end device is specifically: sending, by each antenna panel tothe receive-end device, the data stream corresponding to the DMRS portallocated to the antenna panel.

In a possible design, before the mapping, by each transmit-end device, acodeword to a data stream corresponding to a DMRS port allocated to thetransmit-end device, the method further includes: sending, by one of theat least two transmit-end devices, indication information to thereceive-end device, where the indication information is used to indicatethe plurality of DMRS ports allocated to the receive-end device.

In a possible design, before the mapping, by each transmit-end device, acodeword to a data stream corresponding to a DMRS port allocated to thetransmit-end device, the method further includes: sending, by the sametransmit-end device, indication information to the receive-end device,where the indication information is used to indicate the plurality ofDMRS ports allocated to the receive-end device.

In various aspects and possible designs of this embodiment of thepresent invention, a quantity of the plurality of data streams (in otherwords, a quantity of the plurality of DMRS ports) is less than or equalto 4, but may not be limited thereto. For example, the technicalsolution provided in this embodiment of the present invention may beapplied to a scenario in which a quantity of data streams is less thanor equal to 4, but is not applied to a scenario in which a quantity ofdata streams is greater than 4. Further, in the scenario in which thequantity of data streams is less than or equal to 4, the technicalsolution provided in this embodiment of the present invention may beapplied to a scenario in which the quantity of data streams is 3 and/or4 (in other words, the quantity of the plurality of data streams is 3and/or 4), but is not applied to a scenario in which the quantity of theplurality of data streams is 4. Certainly, the technical solutionprovided in this embodiment of the present invention may not be limitedto the foregoing scenarios.

According to a second aspect of the embodiments of the presentinvention, a data receiving method is provided. The method includes:receiving a plurality of data streams through a plurality of DMRS ports,where the plurality of DMRS ports belong to at least two port groups,DMRS ports in each port group satisfy a quasi co-location QCLrelationship, and any DMRS port in each port group and any DMRS port inany other port group satisfy a non-quasi co-location Non-QCLrelationship; and restoring, by a receive-end device for each of the atleast two port groups, a codeword based on a data stream correspondingto a DMRS port that is in the plurality of DMRS ports and that is in theport group.

In a possible design, before the receiving a plurality of data streams,the method further includes: receiving indication information, where theindication information is used to indicate the plurality of DMRS ports.

In a possible design, a quantity of the plurality of data streams (inother words, a quantity of the plurality of DMRS ports) is less than orequal to 4, but may not be limited thereto. For example, the technicalsolution provided in this embodiment of the present invention may beapplied to a scenario in which a quantity of data streams is less thanor equal to 4, but is not applied to a scenario in which a quantity ofdata streams is greater than 4. Further, in the scenario in which thequantity of data streams is less than or equal to 4, the technicalsolution provided in this embodiment of the present invention may beapplied to a scenario in which the quantity of data streams is 3 and/or4 (in other words, the quantity of the plurality of data streams is 3and/or 4), but is not applied to a scenario in which the quantity of theplurality of data streams is 4. Certainly, the technical solutionprovided in this embodiment of the present invention may not be limitedto the foregoing scenarios.

According to a third aspect of the embodiments of the present invention,a data receiving method is provided. The method includes: receiving aplurality of data streams through a plurality of DMRS ports, where theplurality of DMRS ports belong to a same port group, and DMRS ports inthe port group satisfy a quasi co-location QCL relationship; andrestoring a codeword based on the plurality of data streams.

In a possible design, before the receiving a plurality of data streams,the method further includes: receiving indication information, where theindication information is used to indicate the plurality of DMRS ports.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

In the foregoing various aspects and possible designs, the indicationinformation is downlink control information DCI.

The data stream is also referred to as a data layer.

According to a fourth aspect of the embodiments of the presentinvention, a transmit-end device is provided. The transmit-end device isconfigured to send, together with at least one other transmit-enddevice, a plurality of data streams to a receive-end device through aplurality of demodulation reference signal DMRS ports, where theplurality of DMRS ports belong to at least two port groups, DMRS portsin each port group satisfy a quasi co-location QCL relationship, and anyDMRS port in each port group and any DMRS port in any other port groupsatisfy a non-quasi co-location Non-QCL relationship. The plurality ofDMRS ports are allocated to the transmit-end device and the at least oneother transmit-end device, DMRS ports allocated to the transmit-enddevice and each of the at least one other transmit-end device belong toa same port group. The transmit-end device includes: a mapping module,configured to map a codeword to a data stream corresponding to a DMRSport allocated to the transmit-end device; and a transmitting module,configured to send, to the receive-end device, the data streamcorresponding to the DMRS port allocated to the transmit-end device.

In a possible design, the transmit-end device and the at least one othertransmit-end device are at least two antenna panels of a sametransmit-end device; the mapping module is disposed in the sametransmit-end device, and the mapping module is specifically configuredto map, for each antenna panel, a codeword to a data streamcorresponding to a DMRS port allocated to the antenna panel; and thetransmitting module is disposed in the same transmit-end device, and thetransmitting module is specifically configured to: send, by each antennapanel to the receive-end device, the data stream corresponding to theDMRS port allocated to the antenna panel.

In a possible design, the transmitting module is further configured tosend indication information to the receive-end device, where theindication information is used to indicate the plurality of DMRS portsallocated to the receive-end device.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

According to a fifth aspect of the embodiments of the present invention,a receive-end device is provided. The receive-end device includes: areceiving module, configured to receive a plurality of data streamsthrough a plurality of DMRS ports, where the plurality of DMRS portsbelong to at least two port groups, DMRS ports in each port groupsatisfy a quasi co-location QCL relationship, and any DMRS port in eachport group and any DMRS port in any other port group satisfy a non-quasico-location Non-QCL relationship; and a restoration module, configuredto restore, for each of the at least two port groups, a codeword basedon a data stream corresponding to a DMRS port that is in the pluralityof DMRS ports and that is in the port group.

In a possible design, the receiving module is further configured toreceive indication information, where the indication information is usedto indicate the plurality of DMRS ports.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

According to a sixth aspect of the embodiments of the present invention,a receive-end device is provided. The receive-end device includes: areceiving module, configured to receive a plurality of data streamsthrough a plurality of DMRS ports, where the plurality of DMRS portsbelong to a same port group, and DMRS ports in the port group satisfy aquasi co-location QCL relationship; and a restoration module, configuredto restore a codeword based on the plurality of data streams.

In a possible design, the receiving module is further configured toreceive indication information, where the indication information is usedto indicate the plurality of DMRS ports.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

In the foregoing various aspects and designs of the embodiments of thepresent invention, the indication information may be downlink controlinformation DCI.

According to a seventh aspect of the embodiments of the presentinvention, a data sending method is provided. The method is used forsending a plurality of data streams to a receive-end device through aplurality of demodulation reference signal DMRS ports, where theplurality of DMRS ports belong to at least two port groups, DMRS portsin each port group satisfy a quasi co-location QCL relationship, and anyDMRS port in each port group and any DMRS port in any other port groupsatisfy a non-quasi co-location Non-QCL relationship. The plurality ofDMRS ports are allocated to a same transmit-end device. For each portgroup, the method includes: mapping, by the transmit-end device, acodeword to a data stream corresponding to a DMRS port that is in theplurality of DMRS ports and that is in the port group; and sending, bythe transmit-end device, the data stream to the receive-end device.

In a possible design, the method further includes: sending, by thetransmit-end device, indication information to the receive-end device,where the indication information is used to indicate the plurality ofDMRS ports allocated to the receive-end device.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

According to an eighth aspect of the embodiments of the presentinvention, a transmit-end device is provided. The transmit-end device isconfigured to send a plurality of data streams to a receive-end devicethrough a plurality of demodulation reference signal DMRS ports, wherethe plurality of DMRS ports belong to at least two port groups, DMRSports in each port group satisfy a quasi co-location QCL relationship,and any DMRS port in each port group and any DMRS port in any other portgroup satisfy a non-quasi co-location Non-QCL relationship. Theplurality of DMRS ports are allocated to the transmit-end device. Thetransmit-end device includes: a mapping module, configured to map, foreach port group, a codeword to a data stream corresponding to a DMRSport that is in the plurality of DMRS ports and that is in the portgroup; and a transmitting module, configured to send the data stream tothe receive-end device.

In a possible design, the method further includes: the transmittingmodule is further configured to send indication information to thereceive-end device, where the indication information is used to indicatethe plurality of DMRS ports allocated to the receive-end device.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

To sum up, the embodiments of the present invention provide a datasending method. The method is used for sending a plurality of datastreams to a receive-end device through a plurality of demodulationreference signal DMRS ports, where the plurality of DMRS ports belong toat least two port groups, DMRS ports in each port group satisfy a quasico-location QCL relationship, and any DMRS port in each port group andany DMRS port in any other port group satisfy a non-quasi co-locationNon-QCL relationship. For each port group, the method includes: mappinga codeword into a data stream corresponding to a DMRS port that is inthe plurality of DMRS ports and that is in the port group; and sendingthe data stream to the receive-end device.

In a possible design, the method further includes: sending indicationinformation to the receive-end device, where the indication informationis used to indicate the plurality of DMRS ports allocated to thereceive-end device.

In a possible design, a quantity of the plurality of data streams isless than or equal to 4.

In a possible design, the plurality of DMRS ports may be allocated to asame transmit-end device; or may be allocated to a plurality of antennapanels of a same transmit-end device, where DMRS ports allocated to eachantenna panel belong to a same port group; or may be allocated to aplurality of transmit-end devices serving a same receive-end device (forexample, based on a coordinated multi-point (CoMP) related technology),where DMRS ports allocated to each transmit-end device belong to a sameport group. In addition, the DMRS ports may alternatively be allocatedto one or more transmit-end devices in another manner, for example, butnot limited to, various feasible combinations of the foregoing severalmanners.

Correspondingly, an embodiment of the present invention further providesa data receiving method, including: receiving a plurality of datastreams through a plurality of DMRS ports, where the plurality of DMRSports belong to a same port group or at least two port groups, DMRSports in each port group satisfy a quasi co-location QCL relationship,and any DMRS port in each port group and any DMRS port in any other portgroup satisfy a non-quasi co-location Non-QCL relationship; andrestoring, by a receive-end device for the same port group or each ofthe at least two port groups, a codeword based on a data streamcorresponding to a DMRS port that is in the plurality of DMRS ports andthat is in the port group.

In a possible design, before the receiving a plurality of data streams,the method further includes: receiving indication information, where theindication information is used to indicate the plurality of DMRS ports.

A quantity of the plurality of data streams is less than or equal to 4.

It is easily understood that, on a side of the receive-end device, thereceive-end device may not need to be concerned about whether theplurality of DMRS ports come from a same transmit-end device, aplurality of antenna panels of a same transmit-end device, or aplurality of transmit-end devices.

Quasi co-location (QCL) is usually used to describe similar large-scalefading, similar spatial directions (for example, but not limited to,beam directions), and the like. Therefore, non-quasi co-location(Non-QCL) is usually used to describe different large-scale fading,different spatial directions, and the like. Related content of the QCLand the non-QCL has been clearly described in the prior art, andtherefore, is not described herein.

During actual transmission, an information bit is usually divided in aform of a transport block (TB), and a transport block may be a codeword(CW). For content related to the TB and the CW, refer to the prior art.

Usually, DMRS ports supported by a system may be grouped into aplurality of port groups, DMRS ports in each port group satisfy a QCLrelationship, and any DMRS port in each port group and any DMRS port inany other port group satisfy a non-QCL relationship. When a plurality oftransmit-end devices serve a same receive-end device, DMRS portsallocated to each transmit-end device come from a same port group. Forexample, DMRS ports 0 to 9 may be grouped into two port groups, namely,a port group 1 and a port group 2, where the DMRS ports 0 to 4 belong tothe port group 1, and the DMRS ports 5 to 9 belong to the port group 2.When DMRS ports are allocated to a transmit-end device, any quantity ofDMRS ports in the port group 1 may be allocated to the transmit-enddevice, or any quantity of DMRS ports in the port group 2 may beallocated to the transmit-end device. In addition, regardless of whethera receive-end device is served by a plurality of transmit-end devices ora single transmit-end device, DMRS ports allocated to a sametransmit-end device may come from a same port group or from differentport groups. For example, when the DMRS ports come from a same portgroup, the port 1 and the port 2 in the port group 1 may be allocated tothe transmit-end device. When the DMRS ports come from different portgroups, the ports 2 and 3 in the port group 1 and the ports 8 and 9 inthe port group 2 may be allocated to the transmit-end device. It iseasily understood that, when DMRS ports allocated to a same transmit-enddevice come from different port groups, wireless transmission performedby the transmit-end device through the DMRS ports in the different portgroups has a non-QCL characteristic, for example, has differentlarge-scale fading, different spatial directions, or the like. When DMRSports allocated to a same transmit-end device come from a same portgroup, wireless transmission performed by the transmit-end devicethrough the DMRS ports in the same port group has a QCL characteristic,for example, has similar large-scale fading, similar spatial directions,or the like.

For related content of grouping DMRS ports into a plurality of portgroups, refer to the prior art. For example, a grouping status may bepreset in the transmit-end device and the receive-end device beforedelivery, or the transmit-end device may notify the receive-end deviceof a grouping status of DMRS ports. For example, but not limited tothat, the transmit-end device notifies the receive-end device of thegrouping status by using a Radio Resource Control (RRC) message, forexample, but not limited to, periodically or when the receive-end deviceaccesses a communications network. When DMRS ports are grouped into aplurality of port groups, a DMRS port may be allocated to thetransmit-end device based on a grouping status and a specificrequirement (for example, various application scenarios, such as CoMP).

The plurality of transmit-end devices may be a plurality of transmit-enddevices, or may be a plurality of antenna panels of a same transmit-enddevice. The transmit-end device may be, for example, but not limited to,a base station. The receive-end device may be, for example, but notlimited to, a terminal.

For the process of mapping the codeword to the data stream and theprocess of restoring the codeword from the data stream, refer to theprior art.

When the plurality of transmit-end devices serve a same receive-enddevice, the indication information may be sent by one of the pluralityof transmit-end devices. In this case, the transmit-end device sendingthe indication information may be referred to as a serving device, andother transmit-end devices may be referred to as coordinating devices.

The data stream may also be referred to as a data layer, and usually,may be obtained by performing layer mapping on a codeword. For aspecific process, refer to the prior art.

The steps in the foregoing method may be performed by one or moreprocessors, or may be performed by one or more processors executing aprogram.

Functions of the modules of the transmit-end device and the receive-enddevice may be performed by one or more processors, or may be performedby one or more processors executing a program.

All or some of the foregoing embodiments may be implemented by usingsoftware, hardware, firmware, or any combination thereof. When asoftware program is used to implement the embodiments, the embodimentsmay be implemented completely or partially in a form of a computerprogram product. The computer program product includes one or morecomputer instructions. When the computer program instructions are loadedand executed on a computer, the procedures or functions according to theembodiments of this application are all or partially generated. Thecomputer may be a general-purpose computer, a special-purpose computer,a computer network, or other programmable apparatuses. The computerinstructions may be stored in a computer-readable storage medium or maybe transmitted from a computer-readable storage medium to anothercomputer-readable storage medium. For example, the computer instructionsmay be transmitted from a website, computer, server, or data center toanother website, computer, server, or data center in a wired (forexample, a coaxial cable, an optical fiber, or a digital subscriber line(DSL)) or wireless (for example, infrared, radio, or microwave) manner.The computer-readable storage medium may be any usable medium accessibleby a computer, or a data storage device, such as a server or a datacenter, integrating one or more usable media. The usable medium may be amagnetic medium (for example, a floppy disk, a hard disk, or a magnetictape), an optical medium (for example, a DVD), a semiconductor medium(for example, a solid state disk (SSD)), or the like.

Although this application is described with reference to theembodiments, in a process of implementing this application that claimsprotection, a person skilled in the art may understand and implementanother variation of the disclosed embodiments by viewing theaccompanying drawings, disclosed content, and the appended claims. Inthe claims, “comprising” does not exclude another component or anotherstep, and “a” or “one” does not exclude a meaning of plurality. A singleprocessor or another unit may implement several functions enumerated inthe claims. Some measures are recorded in dependent claims that aredifferent from each other, but this does not mean that these measurescannot be combined to produce a better effect.

Although this application is described with reference to specificfeatures and the embodiments thereof, obviously, various modificationsand combinations may be made to them without departing from the spiritand scope of this application. Correspondingly, the specification andaccompanying drawings are merely example description of this applicationdefined by the appended claims, and is considered as covering any andall modifications, variations, combinations, or equivalents within thescope of this application. Obviously, a person skilled in the art canmake various modifications and variations to this application withoutdeparting from the spirit and scope of this application. Thisapplication is intended to cover these modifications and variations ofthis application provided that they fall within the scope of protectiondefined by the claims of this application and their equivalenttechnologies.

1. A demodulation reference signal (DMRS) receiving method carried outby a receive end, the method comprising: receiving a DMRS indicationinformation that indicates a code division multiplexing (CDM) groupinformation of an antenna port, wherein the CDM group informationcomprises a number of CDM groups; and assisting in demodulating a databased on the DMRS indication information, wherein the number of CDMgroups is a number of CDM groups that have a possibility of beingoccupied or co-scheduled in a system and that are not used fortransmitting data.
 2. The method according to claim 1, wherein a DMRSconfiguration information corresponding to a current DMRS transmissionscheme is determined from a plurality of groups of DMRS configurationinformation, and the DMRS indication information is obtained based onthe DMRS configuration information, wherein each group of DMRSconfiguration information comprises a plurality of pieces of DMRSconfiguration information.
 3. The method according to claim 2, wherein avalue of 1 for the number of CDM groups indicates that a CDM group 1 isoccupied or co-scheduled; wherein a value of 2 for the number of CDMgroups indicates that a CDM group 1 and a CDM group 2 are occupied orco-scheduled; and wherein a value of 3 for the number of CDM groupsindicates that a CDM group 1, a CDM group 2, and a CDM group 3 areoccupied or co-scheduled.
 4. The method according to claim 1, whereinthe DMRS configuration information comprises a DMRS symbol information.5. The method according to claim 4, wherein in the DMRS configurationinformation, specific DMRS port mapping rules of a DMRS type 1 and aDMRS type 2 are as follows: for a 1-symbol DMRS type 1, ports comprisedin the CDM group 1 are {0, 1}, and ports comprised in the CDM group 2are {2, 3}; for a 2-symbol DMRS type 1, ports comprised in the CDM group1 are {0, 1, 4, 5}, and ports comprised in the CDM group 2 are {2, 3, 6,7}; for a 1-symbol DMRS type 2, ports comprised in the CDM group 1 are{0, 1}, ports comprised in the CDM group 2 are {2, 3}, and portscomprised in the CDM group 3 are {4, 5}; and for a 2-symbol DMRS type 2,ports comprised in the CDM group 1 are {0, 1, 6, 7}, ports comprised inthe CDM group 2 are {2, 3, 8, 9}, and ports comprised in the CDM group 3are {4, 5, 10, 11}.
 6. The method according to claim 5, wherein in theDMRS configuration information corresponding to the DMRS type 1, acorrespondence between a number of CDM groups, a port, and a number ofsymbols satisfies a correspondence shown by one or more rows in thefollowing table: One Codeword (≤4 Layers) Two Codewords (>4 Layers) RMI(number of RMI (number of co-scheduled number of Value co-schedulednumber of Value CDM groups) UE Rank Port symbols (value) CDM groups) UERank ports symbols 0 1 1 0 1 0 Reserved reserved reserved 1 1 1 1 1 1 1Reserved reserved reserved 1 2 1 2 0, 1 1 2 Reserved reserved reserved 13 2 1 0 1 3 Reserved reserved reserved 1 4 2 1 1 1 4 Reserved reservedreserved 1 5 2 1 2 1 5 Reserved reserved reserved 1 6 2 1 3 1 6 Reservedreserved reserved 1 7 2 2 0, 1 1 7 Reserved reserved reserved 1 8 2 2 2,3 1 8 Reserved reserved reserved 1 9 2 3 0-2 1 9 Reserved reservedreserved 1 10 2 4 0-3 1 10 Reserved reserved reserved 1 11 1 1 0 2 11 25 0-2, 4, 5 2 12 1 1 1 2 12 2 6 0-5 2 13 1 1 4 2 13 2 7 0-6 2 14 1 1 5 214 2 8 0-7 2 15 1 2 0, 1 2 15 Reserved reserved reserved 2 16 1 2 4-5 216 Reserved reserved reserved 2 17 1 3 0, 1, 4 2 17 Reserved reservedreserved 2 18 1 4 0, 1, 4, 5 2 18 Reserved reserved reserved 2 19 2 1 02 19 Reserved reserved reserved 2 20 2 1 1 2 20 Reserved reservedreserved 2 21 2 1 2 2 21 Reserved reserved reserved 2 22 2 1 3 2 22Reserved reserved reserved 2 23 2 1 4 2 23 Reserved reserved reserved 224 2 1 5 2 24 Reserved reserved reserved 2 25 2 1 6 2 25 Reservedreserved reserved 2 26 2 1 7 2 26 Reserved reserved reserved 2 27 2 2 0,1 2 27 Reserved reserved reserved 2 28 2 2 2, 3 2 28 Reserved reservereserved 2 29 2 2 4, 5 2 29 Reserved reserved reserved 2 30 2 2 6, 7 230 Reserved reserved reserved 2 31 2 3 0, 1, 4 2 31 Reserved reservedreserved 2 32 2 3 2, 3, 6 2 32 Reserved reserved reserved 2 33 2 4 0, 1,4, 5 2 33 Reserved reserved reserved 2 34 2 4 2, 3, 6, 7 2 34 Reservedreserved reserved 2 35 2 2 0, 2 1 35 2 5 0-4 2 36 2 2 0, 2 2 36 2 6 0-4,6 2 37 2 3 0-2 2 37 Reserved reserved reserved reserved 38 2 4 0-3 2 38Reserved reserved reserved reserved


7. The method according to claim 5, wherein in the DMRS configurationinformation corresponding to the DMRS type 2, a correspondence between anumber of CDM groups, a port, and a number of symbols satisfies acorrespondence shown by one or more rows in the following table: OneCodeword (≤4 Layers) Two Codewords (>4 Layers) RMI (number of RMI(number of co-scheduled number of co-scheduled number of Value CDMgroups) UE rank ports symbols Value CDM groups) UE rank ports symbols 01 1 0 1 0 3 5 0-4 1 1 1 1 1 1 1 3 6 0-5 1 2 1 2 0, 1 1 2 Reservedreserved reserved 1 3 2 1 0 1 3 Reserved reserved reserved 1 4 2 1 1 1 4Reserved reserved reserved 1 5 2 1 2 1 5 Reserved reserved reserved 1 62 1 3 1 6 Reserved reserved reserved 1 7 2 2 0, 1 1 7 Reserved reservedreserved 1 8 2 2 2, 3 1 8 Reserved reserved reserved 1 9 2 3 0-2 1 9Reserved reserved reserved 1 10 2 4 0-3 1 10 Reserved reserved reserved1 11 3 1 0 1 11 Reserved reserved reserved 1 12 3 1 1 1 12 Reservedreserved reserved 1 13 3 1 2 1 13 Reserved reserved reserved 1 14 3 1 31 14 Reserved reserved reserved 1 15 3 1 4 1 15 Reserved reservedreserved 1 16 3 1 5 1 16 Reserved reserved reserved 1 17 3 2 0, 1 1 17Reserved reserved reserved 1 18 3 2 2, 3 1 18 Reserved reserved reserved1 19 3 2 4, 5 1 19 Reserved reserved reserved 1 20 3 3 0-2 1 20 Reservedreserved reserved 1 21 3 3 3-5 1 21 Reserved reserved reserved 1 22 3 40-3 1 22 Reserved reserved reserved 1 23 1 1 0 2 23 2 5 0-2, 6, 7 2 24 11 1 2 24 2 6 0-3, 6, 7 2 25 1 1 6 2 25 2 7 0-3, 6-8 2 26 1 1 7 2 26 2 80-3, 6-9 2 27 1 2 0, 1 2 27 Reserved reserved reserved 2 28 1 2 6, 7 228 Reserved reserved reserved 2 29 1 3 0, 1, 6 2 29 Reserved reservedreserved 2 30 1 4 0, 1, 6, 7 2 30 Reserved reserved reserved 2 31 2 1 02 31 Reserved reserved reserved 2 32 2 1 1 2 32 Reserved reservedreserved 2 33 2 1 2 2 33 Reserved reserved reserved 2 34 2 1 3 2 34Reserved reserved reserved 2 35 2 1 6 2 35 Reserved reserved reserved 236 2 1 7 2 36 Reserved reserved reserved 2 37 2 1 8 2 37 Reservedreserved reserved 2 38 2 1 9 2 38 Reserved reserved reserved 2 39 2 2 0,1 2 39 Reserved reserved reserved 2 40 2 2 2, 3 2 40 Reserved reservedreserved 2 41 2 2 6, 7 2 41 Reserved reserved reserved 2 42 2 2 8, 9 242 Reserved reserved reserved 2 43 2 3 0, 1, 6 2 43 Reserved reservedreserved 2 44 2 3 2, 3, 8 2 44 Reserved reserved reserved 2 45 2 4 0, 1,6, 7 2 45 Reserved reserved reserved 2 46 2 4 2, 3, 8, 9 2 46 Reservedreserved reserved 2 47 3 1 0 2 47 Reserved reserved reserved 2 48 3 1 12 48 Reserved reserved reserved 2 49 3 1 2 2 49 Reserved reservedreserved 2 50 3 1 3 2 50 Reserved reserved reserved 2 51 3 1 4 2 51Reserved reserved reserved 2 52 3 1 5 2 52 Reserved reserved reserved 253 3 1 6 2 53 Reserved reserved reserved 2 54 3 1 7 2 54 Reservedreserved reserved 2 55 3 1 8 2 55 Reserved reserved reserved 2 56 3 1 92 56 Reserved reserved reserved 2 57 3 1 10  2 57 Reserved reservedreserved 2 58 3 1 11  2 58 Reserved reserved reserved 2 59 3 2 0, 1 2 59Reserved reserved reserved 2 60 3 2 2, 3 2 60 Reserved reserved reserved2 61 3 2 4, 5 2 61 Reserved reserved reserved 2 62 3 2 6, 7 2 62Reserved reserved reserved 2 63 3 2 8, 9 2 63 Reserved reserved reserved2 64 3 2 10, 11 2 64 Reserved reserved reserved 2 65 3 3 0, 1, 6 2 65Reserved reserved reserved 2 66 3 3 2, 3, 8 2 66 Reserved reservedreserved 2 67 3 3 4, 5, 10 2 67 Reserved reserved reserved 2 68 3 4 0,1, 6, 7 2 68 Reserved reserved reserved 2 69 3 4 2, 3, 8, 9 2 69Reserved reserved reserved 2 70 3 4 4, 5, 10, 11 2 70 Reserved reservedreserved 2 71 2 2 0, 2 1 71 3 5 0-4 2 72 3 3 0, 2, 4 1 72 2 5 0-3, 6 273 3 4 0-2, 4 1 73 3 6 0-5 2 74 2 2 0, 2 2 74 2 6 0-3, 6, 8 2 75 3 3 0,2, 4 2 75 3 7 0-6 2 76 2 4 0, 1, 2, 3 2 76 3 8 0-6, 8 2 77 3 4 0, 1, 2,4 2 77 3 8 0-7 2 78 3 3 2, 3, 7 2 78 Reserved reserved reserved reserved79 3 3 8, 9, 4 2 79 Reserved reserved reserved reserved 80 3 3 10, 11, 52 80 Reserved reserved reserved reserved 81 3 3 7, 9, 11 2 81 Reservedreserved reserved reserved


8. The method according to claim 1, wherein an available range of theDMRS configuration information is configured by using an RRC signaling,and the available range is determined based on at least one of the groupconsisting of; a DMRS symbol information, and a maximum number ofsymbols of a DMRS.
 9. The method according to claim 1, wherein anavailable range of the DMRS configuration information is associated witha parameter that is in a Radio Resource Control (RRC) signaling and thatindicates a maximum number of symbols of a DMRS.
 10. A terminal,comprising: a transceiver; a processor; and a non-transitorycomputer-readable medium including computer-executable instructionsthat, when executed by the processor, facilitate the terminal carryingout a method comprising: receiving, by the transceiver cooperativelyoperating with the processor, a demodulation reference signal (DMRS)indication information that indicates a code division multiplexing (CDM)group information of an antenna port, wherein the CDM group informationcomprises a number of CDM groups; and demodulating, by the processor, adata based on the DMRS indication information received by thetransceiver; and wherein the number of CDM groups is a number of CDMgroups that have a possibility of being occupied or co-scheduled in asystem and that are not used for transmitting data.
 11. The terminalaccording to claim 10, wherein a DMRS configuration informationcorresponding to a current DMRS transmission scheme is determined from aplurality of groups of DMRS configuration information, and the DMRSindication information is obtained based on the DMRS configurationinformation, wherein each group of DMRS configuration informationcomprises a plurality of pieces of DMRS configuration information. 12.The terminal according to claim 10, wherein a value of 1 for the numberof CDM groups indicates that a CDM group 1 is occupied or co-scheduled;wherein a value of 2 for the number of CDM groups indicates that a CDMgroup 1 and a CDM group 2 are occupied or co-scheduled; and wherein avalue of 3 for the number of CDM groups indicates that a CDM group 1, aCDM group 2, and a CDM group 3 are occupied or co-scheduled.
 13. Theterminal according to claim 10, wherein the DMRS configurationinformation further comprises a DMRS symbol information.
 14. Theterminal according to claim 10 wherein in the DMRS configurationinformation, specific DMRS port mapping rules of a DMRS type 1 and aDMRS type 2 are as follows: for a 1-symbol DMRS type 1, ports comprisedin the CDM group 1 are {0, 1}, and ports comprised in the CDM group 2are {2, 3}; for a 2-symbol DMRS type 1, ports comprised in the CDM group1 are {0, 1, 4, 5}, and ports comprised in the CDM group 2 are {2, 3, 6,7}; for a 1-symbol DMRS type 2, ports comprised in the CDM group 1 are{0, 1}, ports comprised in the CDM group 2 are {2, 3}, and portscomprised in the CDM group 3 are {4, 5}; and for a 2-symbol DMRS type 2,ports comprised in the CDM group 1 are {0, 1, 6, 7}, ports comprised inthe CDM group 2 are {2, 3, 8, 9}, and ports comprised in the CDM group 3are {4, 5, 10, 11}.
 15. The terminal according to claim 14, wherein inthe DMRS configuration information corresponding to the DMRS type 1, acorrespondence between a number of CDM groups, a port, and a number ofsymbols satisfies a correspondence shown by one or more rows in thefollowing table: One Codeword (≤4 Layers) Two Codewords (>4 Layers) RMI(number of RMI (number of co-scheduled number of co-scheduled number ofValue CDM groups) UE rank Port symbols Value CDM groups) UE rank Portsymbols 0 1 1 0 1 0 reserved Reserved reserved 1 1 1 1 1 1 1 reservedreserved reserved 1 2 1 2 0, 1 1 2 reserved reserved reserved 1 3 2 1 01 3 reserved reserved reserved 1 4 2 1 1 1 4 reserved reserved reserved1 5 2 1 2 1 5 reserved reserved reserved 1 6 2 1 3 1 6 reserved reservedreserved 1 7 2 2 0, 1 1 7 reserved reserved reserved 1 8 2 2 2, 3 1 8reserved reserved reserved 1 9 2 3 0-2 1 9 reserved reserved reserved 110 2 4 0-3 1 10 reserved reserved reserved 1 11 1 1 0 2 11 2 5 0-2, 4, 52 12 1 1 1 2 12 2 6 0-5 2 13 1 1 4 2 13 2 7 0-6 2 14 1 1 5 2 14 2 8 0-72 15 1 2 0, 1 2 15 reserved reserved reserved 2 16 1 2 4-5 2 16 reservedreserved reserved 2 17 1 3 0, 1, 4 2 17 reserved reserved reserved 2 181 4 0, 1, 4, 5 2 18 reserved reserved reserved 2 19 2 1 0 2 19 reservedreserved reserved 2 20 2 1 1 2 20 reserved reserved reserved 2 21 2 1 22 21 reserved reserved reserved 2 22 2 1 3 2 22 reserved reservedreserved 2 23 2 1 4 2 23 reserved reserved reserved 2 24 2 1 5 2 24reserved reserved reserved 2 25 2 1 6 2 25 reserved reserved reserved 226 2 1 7 2 26 reserved reserved reserved 2 27 2 2 0, 1 2 27 reservedreserved reserved 2 28 2 2 2, 3 2 28 reserved reserved reserved 2 29 2 24, 5 2 29 reserved reserved reserved 2 30 2 2 6, 7 2 30 reservedreserved reserved 2 31 2 3 0, 1, 4 2 31 reserved reserved reserved 2 322 3 2, 3, 6 2 32 reserved reserved reserved 2 33 2 4 0, 1, 4, 5 2 33reserved reserved reserved 2 34 2 4 2, 3, 6, 7 2 34 reserved reservedreserved 2 35 2 2 0, 2 1 35 2 5 0-4 2 36 2 2 0, 2 2 36 2 6 0-4, 6 2 37 23 0-2 2 37 reserved reserved reserved reserved 38 2 4 0-3 2 38 reservedreserved reserved reserved


16. The terminal according to claim 14, wherein in the DMRSconfiguration information corresponding to the DMRS type 2, acorrespondence between a number of CDM groups, a port, and a number ofsymbols satisfies a correspondence shown by one or more rows in thefollowing table: One Codeword (≤4 Layers) Two Codewords (>4 Layers) RMI(number of RMI (number of co-scheduled number of co-scheduled number ofValue CDM groups) UE rank Port symbols Value CDM groups) UE rank Portsymbols 0 1 1 0 1 0 3 5 0-4 1 1 1 1 1 1 1 3 6 0-5 1 2 1 2 0, 1 1 2reserved reserved reserved 1 3 2 1 0 1 3 reserved reserved reserved 1 42 1 1 1 4 reserved reserved reserved 1 5 2 1 2 1 5 reserved reservedreserved 1 6 2 1 3 1 6 reserved reserved reserved 1 7 2 2 0, 1 1 7reserved reserved reserved 1 8 2 2 2, 3 1 8 reserved reserved reserved 19 2 3 0-2 1 9 reserved reserved reserved 1 10 2 4 0-3 1 10 reservedreserved reserved 1 11 3 1 0 1 11 reserved reserved reserved 1 12 3 1 11 12 reserved reserved reserved 1 13 3 1 2 1 13 reserved reservedreserved 1 14 3 1 3 1 14 reserved reserved reserved 1 15 3 1 4 1 15reserved reserved reserved 1 16 3 1 5 1 16 reserved reserved reserved 117 3 2 0, 1 1 17 reserved reserved reserved 1 18 3 2 2, 3 1 18 reservedreserved reserved 1 19 3 2 4, 5 1 19 reserved reserved reserved 1 20 3 30-2 1 20 reserved reserved reserved 1 21 3 3 3-5 1 21 reserved reservedreserved 1 22 3 4 0-3 1 22 reserved reserved reserved 1 23 1 1 0 2 23 25 0-2, 6, 7 2 24 1 1 1 2 24 2 6 0-3, 6, 7 2 25 1 1 6 2 25 2 7 0-3, 6-8 226 1 1 7 2 26 2 8 0-3, 6-9 2 27 1 2 0, 1 2 27 reserved reserved reserved2 28 1 2 6, 7 2 28 reserved reserved reserved 2 29 1 3 0, 1, 6 2 29reserved reserved reserved 2 30 1 4 0, 1, 6, 7 2 30 reserved reservedreserved 2 31 2 1 0 2 31 reserved reserved reserved 2 32 2 1 1 2 32reserved reserved reserved 2 33 2 1 2 2 33 reserved reserved reserved 234 2 1 3 2 34 reserved reserved reserved 2 35 2 1 6 2 35 reservedreserved reserved 2 36 2 1 7 2 36 reserved reserved reserved 2 37 2 1 82 37 reserved reserved reserved 2 38 2 1 9 2 38 reserved reservedreserved 2 39 2 2 0, 1 2 39 reserved reserved reserved 2 40 2 2 2, 3 240 reserved reserved reserved 2 41 2 2 6, 7 2 41 reserved reservedreserved 2 42 2 2 8, 9 2 42 reserved reserved reserved 2 43 2 3 0, 1, 62 43 reserved reserved reserved 2 44 2 3 2, 3, 8 2 44 reserved reservedreserved 2 45 2 4 0, 1, 6, 7 2 45 reserved reserved reserved 2 46 2 4 2,3, 8, 9 2 46 reserved reserved reserved 2 47 3 1 0 2 47 reservedreserved reserved 2 48 3 1 1 2 48 reserved reserved reserved 2 49 3 1 22 49 reserved reserved reserved 2 50 3 1 3 2 50 reserved reservedreserved 2 51 3 1 4 2 51 reserved reserved reserved 2 52 3 1 5 2 52reserved reserved reserved 2 53 3 1 6 2 53 reserved reserved reserved 254 3 1 7 2 54 reserved reserved reserved 2 55 3 1 8 2 55 reservedreserved reserved 2 56 3 1 9 2 56 reserved reserved reserved 2 57 3 110  2 57 reserved reserved reserved 2 58 3 1 11  2 58 reserved reservedreserved 2 59 3 2 0, 1 2 59 reserved reserved reserved 2 60 3 2 2, 3 260 reserved reserved reserved 2 61 3 2 4, 5 2 61 reserved reservedreserved 2 62 3 2 6, 7 2 62 reserved reserved reserved 2 63 3 2 8, 9 263 reserved reserved reserved 2 64 3 2 10, 11 2 64 reserved reservedreserved 2 65 3 3 0, 1, 6 2 65 reserved reserved reserved 2 66 3 3 2, 3,8 2 66 reserved reserved reserved 2 67 3 3 4, 5, 10 2 67 reservedreserved reserved 2 68 3 4 0, 1, 6, 7 2 68 reserved reserved reserved 269 3 4 2, 3, 8, 9 2 69 reserved reserved reserved 2 70 3 4 4, 5, 10, 112 70 reserved reserved reserved 2 71 2 2 0, 2 1 71 3 5 0-4 2 72 3 3 0,2, 4 1 72 2 5 0-3, 6 2 73 3 4 0-2, 4 1 73 3 6 0-5 2 74 2 2 0, 2 2 74 2 60-3, 6, 8 2 75 3 3 0, 2, 4 2 75 3 7 0-6 2 76 2 4 0, 1, 2, 3 2 76 3 80-6, 8 2 77 3 4 0, 1, 2, 4 2 77 3 8 0-7 2 78 3 3 2, 3, 7 2 78 reservedreserved reserved reserved 79 3 3 8, 9, 4 2 79 reserved reservedreserved reserved 80 3 3 10, 11, 5 2 80 reserved reserved reservedreserved 81 3 3 7, 9, 11 2 81 reserved reserved reserved reserved


17. The terminal according to claim 10, wherein an available range ofthe DMRS configuration information is configured by using Radio ResourceControl (RRC) signaling, and the available range is determined based onDMRS symbol information or a maximum number of symbols of a DMRS. 18.The terminal according to claim 10, wherein an available range of theDMRS configuration information is associated with a parameter that is inRadio Resource Control (RRC) signaling and that indicates a maximumnumber of symbols of a DMRS.
 19. A chip, comprising at least oneprocessor and an interface, wherein the at least one processor isconfigured to read and execute a program instruction to implement ademodulation reference signal (DMRS) receiving method, comprising:controlling receiving a DMRS indication information that indicates acode division multiplexing (CDM) group information of an antenna port,wherein the CDM group information comprises a number of CDM groups; anddemodulating a data based on the DMRS indication information, whereinthe number of CDM groups is a number of CDM groups that have apossibility of being occupied or co-scheduled in a system and that arenot used for transmitting data.
 20. The chip according to claim 19,wherein a DMRS configuration information corresponding to a current DMRStransmission scheme is determined from a plurality of groups of DMRSconfiguration information, and the DMRS indication information isobtained based on the DMRS configuration information, wherein each groupof DMRS configuration information comprises a plurality of pieces ofDMRS configuration information.
 21. The chip according to claim 20,wherein a value of 1 for the number of CDM groups indicates that a CDMgroup 1 is occupied or co-scheduled; wherein a value of 2 for the numberof CDM groups indicates that a CDM group 1 and a CDM group 2 areoccupied or co-scheduled; and wherein a value of 3 for the number of CDMgroups indicates that a CDM group 1, a CDM group 2, and a CDM group 3are occupied or co-scheduled.
 22. A non-transitory computer storagemedium, wherein the computer non-transitory storage medium stores aninstruction, and when being run on a processing component of a computer,the instruction enables the processing component to perform ademodulation reference signal receiving method comprising: controllingreceiving of a demodulation reference signal (DMRS) indicationinformation that indicates a code division multiplexing (CDM) groupinformation of an antenna port, wherein the CDM group informationcomprises a number of CDM groups; and demodulating a data based on theDMRS indication information, wherein the number of CDM groups is anumber of CDM groups that have a possibility of being occupied orco-scheduled in a system and that are not used for transmitting data.23. The non-transitory computer storage medium according to claim 22,wherein a DMRS configuration information corresponding to a current DMRStransmission scheme is determined from a plurality of groups of DMRSconfiguration information, and the DMRS indication information isobtained based on the DMRS configuration information, wherein each groupof DMRS configuration information comprises a plurality of pieces ofDMRS configuration information.
 24. The non-transitory computer storagemedium according to claim 22, wherein a value of 1 for the number of CDMgroups indicates that a CDM group 1 is occupied or co-scheduled; whereina value of 2 for the number of CDM groups indicates that a CDM group 1and a CDM group 2 are occupied or co-scheduled; and wherein a value of 3for the number of CDM groups indicates that a CDM group 1, a CDM group2, and a CDM group 3 are occupied or co-scheduled.